home *** CD-ROM | disk | FTP | other *** search
Text File | 1995-03-10 | 148.3 KB | 4,486 lines |
-
-
-
-
-
-
-
-
-
- M A I L M A N A G E R
-
- v. 1.0
-
-
-
- Full Integrated
- Tosser/Scanner/Editor/Tick Processor
-
-
- Copyright (C)
- 1994/1995 Pino Aliberti
- All rights reserved
-
-
-
-
- USER MANUAL
-
- Saturday 11-Mar-95
-
-
- Copyright (C)
- 1994/1995 Pino Aliberti
- All rights reserved
-
-
-
-
-
-
-
-
- INDEX
- ---------
-
- 0 INTRODUCTION
- 0.1 Overall
- 0.2 Bonds
- 0.3 Installation
- 0.4 Running Mail Manager
- 0.5 OnLine Help
- 0.6 Features
-
- 1 MAIL MANAGER CONFIGURATION & MM_PREFS
-
- 1.1 System
- 1.1.1 Sysop Names
- 1.1.2 Addresses
- 1.1.3 Groups
-
- 1.2 Misc 1
- 1.2.1 Fonts
- 1.2.2 Tick Commands
- 1.2.3 Archivers
-
- 1.3 Misc 2
- 1.3.1 Variables
- 1.3.1.1 Check Dupes
- 1.3.1.1.1 Messages
- 1.3.1.1.2 Ticks
- 1.3.1.2 Areas List
- 1.3.1.2.1 Show
- 1.3.1.2.2 Order
- 1.3.1.3 PreParse Strings
- 1.3.1.3.1 Kludges
- 1.3.1.3.2 Quoted
- 1.3.1.4 Delete Char
- 1.3.1.5 Switches
- 1.3.1.5.1 5D Origins
- 1.3.1.5.2 Check Domains
- 1.3.1.5.3 Crunch Matrix
- 1.3.1.5.4 Do Backup
- 1.3.1.5.5 Keep Matrix
- 1.3.1.5.6 Keep Sysop
- 1.3.1.5.7 Pack Every Bundle
- 1.3.1.5.8 Quote Kludges
- 1.3.1.5.9 Reflow Messages
- 1.3.1.5.10 Safe Import
- 1.3.1.5.11 Show Kludges
- 1.3.1.5.12 Show PassThrough
- 1.3.1.5.13 Smart Export
- 1.3.1.5.14 Threads Opened
- 1.3.1.5.15 Text Styles
- 1.3.2 Paths
- 1.3.2.1 Editor
- 1.3.2.2 Archive File
- 1.3.2.3 Inbound Dir
- 1.3.2.4 Outbound Dir
- 1.3.2.5 Bad Dir
- 1.3.2.6 Bundle Dir
- 1.3.2.7 Backup Dir
- 1.3.2.8 Tic Dir
- 1.3.2.9 Working Dir
- 1.3.2.10 Temp Pkt Dir
- 1.3.2.11 Nodelist Dir
- 1.3.2.12 Mail Device
- 1.3.2.13 Userlist
- 1.3.2.14 Statistics
- 1.3.3 Sizes
- 1.3.3.1 Task Priority
- 1.3.3.2 Min Free Mem
- 1.3.3.3 Max Pkt Size
- 1.3.3.4 Max Bundle Size
- 1.3.3.5 Commands Stack
- 1.3.4 Logs
- 1.3.4.1 Window
- 1.3.3.2 File
-
- 1.4 Texts
- 1.4.1 Prologues
- 1.4.2 Logos
- 1.4.3 Origins
- 1.4.4 Forward
-
- 1.5 Custom
- 1.5.1 Areas/Messages Commands
- 1.5.2 Browse Commands
-
- 1.6 Nodes
- 1.6.1 Packets
- 1.6.1.1 Archivers
- 1.6.1.2 Packets
- 1.6.1.3 Flavors
- 1.6.1.4 Passwords
- 1.6.2 Groups
- 1.6.3 Areas
- 1.6.4 Misc
- 1.6.4.1 UserFlags
- 1.6.4.2 Can Create Areas
-
- 1.7 Routing
- 1.7.1 Settings
- 1.7.1.1 Original Message
- 1.7.1.2 Action
- 1.7.1.3 To
- 1.7.2 Test
-
- 1.8 Areas
- 1.8.1 Messages
- 1.8.1.1 System
- 1.8.1.1.1 Name
- 1.8.1.1.2 Desc
- 1.8.1.1.3 Path
- 1.8.1.1.4 AltPath
- 1.8.1.1.5 UserFlags
- 1.8.1.1.6 Address
- 1.8.1.1.7 Group
- 1.8.1.2 Nodes
- 1.8.1.3 Texts
- 1.8.1.4 Misc
- 1.8.1.4.1 Read Only
- 1.8.1.4.2 Two pass Import
- 1.8.1.4.3 CharSet
- 1.8.1.4.4 Delete By
- 1.8.1.4.5 Font
- 1.8.1.4.6 Msgbase
- 1.8.1.4.7 Show
- 1.8.1.4.8 Sort
- 1.8.2 Ticks
- 1.8.2.1 System
- 1.8.2.1.1 Desc
- 1.8.2.1.2 Path
- 1.8.2.1.3 AltPath
- 1.8.2.1.4 UserFlags
- 1.8.2.1.5 Address
- 1.8.2.1.6 Group
- 1.8.2.2 Nodes
- 1.8.2.3 Tick Commands
-
-
- 2 MAIL MANAGER GRAPHICAL USER INTERFACE
-
- 2.1 Areas Window
- 2.1.1 Areas List
- 2.1.2 Areas Management
- 2.1.2.1 All
- 2.1.2.2 None
- 2.1.2.3 Import
- 2.1.2.4 Export
- 2.1.2.5 Scan
- 2.1.2.6 Free
- 2.1.2.7 Update
- 2.1.2.8 Optimize
- 2.1.2.9 Delete
- 2.1.2.10 Purge
- 2.1.2.11 Show
- 2.1.2.12 Sort
- 2.1.3 Areas Window Menus
- 2.1.3.1 Project
- 2.1.3.1.1 About
- 2.1.3.1.2 Quit
- 2.1.3.2 Configuration
- 2.1.3.2.1 Edit
- 2.1.3.2.2 Load...
- 2.1.3.2.3 Save
- 2.1.3.2.4 Save As...
- 2.1.3.3 Ticks
- 2.1.3.3.1 Import
- 2.1.3.3.2 Hatch
- 2.1.3.4 Miscellaneous
- 2.1.3.4.1 File Request
- 2.1.3.4.2 Area Statistics
- 2.1.3.4.3 Renumber
- 2.1.3.4.4 Convert Message Base
- 2.1.3.4.5 Deep Scan
- 2.1.3.4.6 Write Stats
- 2.1.3.4.7 Restore Bad
- 2.1.3.5 Domains
- 2.1.3.6 User
-
- 2.2 Messages Window
- 2.2.1 Messages List
- 2.2.2 Messages Management
- 2.2.2.1 All
- 2.2.2.2 None
- 2.2.2.3 Search
- 2.2.2.4 Flags
- 2.2.2.5 R News
- 2.2.2.6 R Slct
- 2.2.2.7 Write
- 2.2.2.8 Forward
- 2.2.2.9 Edit
- 2.2.2.10 Edit Hdr
- 2.2.2.11 Reply
- 2.2.2.12 X Reply
- 2.2.2.13 Show
- 2.2.2.14 Sort
- 2.2.3 Messages Window Menus
- 2.2.3.1 Messages
- 2.2.3.1.1 Delete
- 2.2.3.1.2 Protect
- 2.2.3.1.3 Mark
- 2.2.3.1.4 Archive
- 2.2.3.1.5 Print
- 2.2.3.1.6 Toggle UnReplied Flag
- 2.2.3.2 Miscellaneous
- 2.2.3.2.1 File Request
- 2.2.3.2.2 Areas Window
- 2.2.3.2.3 Areas List
- 2.2.3.2.4 Previous Area
- 2.2.3.2.5 Next Area
- 2.2.3.2.6 Previous UnRead Area
- 2.2.3.2.7 Next UnRead Area
- 2.2.3.2.8 Export Area
- 2.2.3.3 User
-
- 2.3 Browse Window
- 2.3.1 Browse Window Gadgets
- 2.3.1.1 Threads
- 2.3.1.2 Write
- 2.3.1.3 Forward
- 2.3.1.4 Edit
- 2.3.1.5 Edit Hdr
- 2.3.1.6 Reply
- 2.3.1.7 X Reply
- 2.3.2 Browse Window Menus
- 2.3.2.1 Messages
- 2.3.2.1.1 Delete
- 2.3.2.1.2 Protect
- 2.3.2.1.3 Mark
- 2.3.2.1.4 Archive
- 2.3.2.1.5 Print
- 2.3.2.1.6 Toggle UnReplied Flag
- 2.3.2.2 Miscellaneous
- 2.3.2.2.1 File Request
- 2.3.2.2.2 Areas Window
- 2.3.2.2.3 Areas List
- 2.3.2.2.4 Previous Area
- 2.3.2.2.5 Next Area
- 2.3.2.2.6 Previous UnRead Area
- 2.3.2.2.7 Next UnRead Area
- 2.3.2.2.8 Export Area
- 2.3.2.3 Environment
- 2.3.2.3.1 Text Styles
- 2.3.2.3.2 Show Kludges
- 2.3.2.3.3 Quote Kludges
- 2.3.2.4 User
- 2.3.3 Browse Window ShortCuts
- 2.3.3.1 Left
- 2.3.3.2 Right
- 2.3.3.3 Shift+Left
- 2.3.3.4 Shift+Right
- 2.3.3.5 Alt+Left
- 2.3.3.6 Alt+Right
- 2.3.3.7 Control+Left
- 2.3.3.8 Control+Right
- 2.3.3.9 Space
- 2.3.3.10 Shift+Space
- 2.3.3.11 Return
- 2.3.3.12 Del
-
- 2.4 Message Parameters Window
- 2.4.1 From
- 2.4.2 To
- 2.4.3 Subj
- 2.4.4 Origin
- 2.4.5 Flavor
- 2.4.6 Private
- 2.4.7 Reflow Text
- 2.4.8 File Attached
- 2.4.9 Force Address
- 2.4.10 Multi Send
- 2.4.11 Receipt Request
-
-
- 3 MAIL MANAGER AREXX INTERFACE
-
- 3.1 Standard MUI ARexx Commands
- 3.1.1 Quit
- 3.1.2 Hide
- 3.1.3 Show
- 3.1.4 Help
-
- 3.2 Mail Manager Internal ARexx Commands
- 3.2.1 Ticks Management
- 3.2.1.1 MM_ImportTicks
- 3.2.1.2 MM_HatchTick
- 3.2.2 Areas Management
- 3.2.2.1 MM_Import
- 3.2.2.2 MM_Export
- 3.2.2.3 MM_Rescan
- 3.2.2.4 MM_Scan
- 3.2.2.5 MM_Free
- 3.2.2.6 MM_Update
- 3.2.2.7 MM_WriteStats
- 3.2.2.8 MM_Renumber
- 3.2.2.9 MM_Optimize
- 3.2.2.10 MM_Delete
- 3.2.2.11 MM_Purge
- 3.2.2.12 MM_CleanArea
- 3.2.3 Messages Management
- 3.2.3.1 MM_EditMsgFlags
- 3.2.3.2 MM_SearchMsgs
- 3.2.3.3 MM_ReadMsg
- 3.2.3.4 MM_WriteMsg
- 3.2.3.5 MM_EditMsg
- 3.2.3.6 MM_DeleteMsg
- 3.2.4 Configuration Management
- 3.2.4.1 MM_LoadCfg
- 3.2.4.2 MM_SaveCfg
- 3.2.4.3 MM_GetSysop
- 3.2.4.4 MM_GetAddrs
- 3.2.4.5 MM_GetNearestAddr
- 3.2.4.6 MM_GetGroups
- 3.2.4.7 MM_GetGroupAreas
- 3.2.4.8 MM_GetGroupTickAreas
- 3.2.4.9 MM_GetNodes
- 3.2.4.10 MM_GetNodeInfo
- 3.2.4.11 MM_GetCfgPaths
- 3.2.4.12 MM_GetAreas
- 3.2.4.13 MM_GetAreaInfo
- 3.2.4.14 MM_CreateArea
- 3.2.4.15 MM_AddAreaNode
- 3.2.4.16 MM_DelAreaNode
- 3.2.4.17 MM_GetTickAreas
- 3.2.4.18 MM_GetTickAreaInfo
- 3.2.4.19 MM_AddTickAreaNode
- 3.2.4.20 MM_DelTickAreaNode
- 3.2.5 Miscellaneous Management
- 3.2.5.1 MM_GetNodelistNode
- 3.2.5.2 MM_RequestFiles
- 3.2.5.3 MM_AddToFlow
- 3.2.5.4 MM_AreasWin
- 3.2.5.5 MM_WriteLog
- 3.2.5.6 MM_CloseLog
- 3.2.6 Requesters Management
- 3.2.6.1 MM_Requester
- 3.2.6.2 MM_StringReq
- 3.2.6.3 MM_FileReq
- 3.2.6.4 MM_AreaReq
- 3.2.6.5 MM_SingleSelReq
- 3.2.6.6 MM_MultiSelReq
- 3.2.7 Stems Management
- 3.2.7.1 MM_WriteStem
- 3.2.7.2 MM_ReadStem
- 3.2.7.3 MM_SearchInStem
- 3.2.7.4 MM_AddToStem
- 3.2.7.5 MM_SortStem
- 3.2.7.6 MM_SortAddresses
- 3.2.8 Files Management
- 3.2.8.1 MM_CRCFile
- 3.2.8.2 MM_CopyFile
- 3.2.8.3 MM_MoveFile
- 3.2.8.4 MM_DeleteFile
- 3.2.8.5 MM_SetFileNote
-
- 4 MISCELLANEOUS
- 4.1 Support
- 4.2 Registration
- 4.3 About MUI
- 4.4 MUI Hints & Tips
- 4.5 Licence Agreement
- 4.6 Acknowledgements
-
-
-
-
- 0 INTRODUCTION
-
- This document describes, in short, but hopefully thorough, terms how to
- use the different functions in Mail Manager.
- Please read it carefully ! Many of the problems a user can have in the
- use of a program, can be solved by carefully reading the manual.
-
-
- 0.1 Overall
-
- Mail Manager is a Full Integrated Tosser, Scanner, Editor and Tick
- Processor for Nodes and Points using Amiga Computers.
-
- The Mail Manager project was born two years ago with one big aim: to
- create the Mail Management Program the Amiga users have always dream
- about: easy to use as Spot, complete as EMS, smart and intuitive as
- Point Manager. I don't know if Mail Manager has already reached this
- aim, but I've worked really much on it and I hope you will like the
- result.
-
- Mail Manager uses the MagicUserInterface (MUI) by Stefan Stuntz, this
- gives to Mail Manager a unique Graphical User Interface.
- With MUI you can configure almost everything of the Mail Manager GUI,
- besides you can control everything with the mouse or even with the
- keyboard. In order to completelly exploit such a powerful interface
- you should read MUI's documentation carefully.
-
-
- 0.2 Bonds
-
- Mail Manager requires only a few bonds to work properly:
-
- - Kickstart 2.04 or higher
- - MUI 2.0 or higher
-
-
- 0.3 Installation
-
- Please use the appropriate installation icon in the `Install' drawer.
- It uses Commodore's Installer utility and will copy all the files in
- the appropriate directories, it will also add some assignments to your
- User-Startup and will ask you some information to create a default
- configuration. After that you will be immediatelly able to run Mail
- Manager.
-
-
- 0.4 Running Mail Manager
-
- You can run Mail Manager from the Workbench or from the Shell. The
- command line syntax for Mail Manager is:
-
- MM [CFG=<CFG File>] [I]
-
- If you do not specify a configuration file, Mail Manager looks for a
- file called "MM:Config/MailManager.CFG".
- If you specify the 'I' option Mail Manager will start in iconified
- state. Be careful, when Mail Manager is launched in iconified state
- it is not able to report you the possible configuration errors.
-
-
- 0.5 OnLine Help
-
- Mail Manager offers you a powerful OnLine Help function. Wherever you
- are inside Mail Manager and MM_Prefs, you could press the Help Key and
- Mail Manager will show you the right part of the Mail Manager manual.
-
-
- 0.6 Features
-
- Mail Manager...
-
- ... is Faaaaaaaast. Up to 3 times faster than Spot or EMS.
- ... is easy to configure.
- ... is fully localized ( Workbench 2.1 or higher).
- ... is able to manage Tick Files.
- ... is able to manage Echo File Attached.
- ... is able to automatically create new Echo Areas.
- ... is able to manage 4 different types of message bases.
- ... is able to manage 3 different types of Mail Packets.
- ... is able to use full 5 dimensional addressing.
- ... has a powerful ARexx interface.
- ... has a powerful OnLine Help.
- ... has a powerful Threads management.
- ... has a powerful NetMail Routing management.
- ... has powerful Search/Sort/Show functions.
- ... has powerful Quoting routines.
- ... supports multiple character sets.
- ... supports the Nodelist and the Userlist.
- ... uses fast Memory Pools functions.
- ... uses fast asynchronous I/O functions.
- ... is a MUI Application !!!!
- ... has many many other features !
-
-
-
-
-
- 1 MAIL MANAGER CONFIGURATION & MM_PREFS
-
- Mail Manager is a really complex program, nevertheless I've made my best
- to make its configuration as easy as possible.
- The format of its configuration file is plain text so it is possible to
- edit it with a normal TextEditor, however it is better to use MM_Prefs
- to edit the Mail Manager configuration, as it prevents any kind of
- syntax error and makes everything easier.
- You can start MM_Prefs from inside Mail Manager with the 'Edit' item of
- the Configuration Menu, or, if Mail Manager is not running, from either
- the Shell or the Workbench.
- MM_Prefs depends heavily on the use of MUI's Register Objects; in order
- to completelly exploit the properties of these objects you have to set
- "Register Level" to at least 3 and "Max Pages" to at least 8 in the
- "Lists" page of MUIPrefs, otherwise MUI's Register Object will switch
- back to a standard cycle gadget.
-
-
-
- 1.1 System
-
- 1.1.1 Sysop Names
-
- Here you can insert the names you want to use in the Messages Areas.
- The entry labeled as <Default> is the Default Sysop Name, it will be
- used in all the areas where you have not specified a particular
- Sysop Name.
- In the "Label" string gadget you have to insert a symbolic name
- associated to the Sysop Name, all the rest of the system will
- refer to the Sysop Name with this label.
- In the "Name" string gadget you have to insert the Sysop Name
- itself.
-
-
- 1.1.2 Addresses
-
- Here you can insert all your Addresses. You have to enter the
- Address in 5D format ( <zone>:<net>/<node>.<point>@<domain> ). The
- domain string should not include the extension ( for example use
- "fidonet" and not "fidonet.org" ) and should not be longer than 8
- chrs; this is a limit introduced by Fidonet standards, not from Mail
- Manager itself.
- The Fakenet is a Fake Address used, for managing points, with stone
- aged systems that only could manage 2D addresses. If you want to
- disable the use of the FakeNet also with 2D systems you should set
- it to 0.
- In a standard configuration you have to use a single Address for
- every Domain, if you have more than one Address for every Domain you
- should flag them as Akas; this way Mail Manager won't scan them
- during the search for your address nearer to a particular node.
- As a general rule, you have to flag as Aka all the Addresses you do
- not want to normally use as originating address of your messages.
-
-
- 1.1.3 Groups
-
- Here you can insert all the Groups. Groups are really useful only
- for Full Nodes that use them mainly for AreaFix. Anyway also a
- simple Point could use them for grouping together some areas with
- the same characteristics. If you do not need Groups, you could
- define a single group and link all the areas to this group.
-
-
-
-
- 1.2 Misc 1
-
- 1.2.1 Fonts
-
- By default Mail Manager uses the fonts configured with MUIPrefs.
- Anyway it is possible that you want to use a particular font to show
- the text of a message ( for example an IBM font for an area with an
- IBM charset ). Here you can insert all the fonts you plan to use
- inside the messages areas.
- In the "Label" string gadget you have to insert a symbolic name
- associated to the Font, all the rest of the system will refer the
- Font with this label.
- In the "Font" string gadget you have to insert the Font itself in
- the format <fontname>/<fontsize>.
-
-
- 1.2.2 Tick Commands
-
- Mail Manager offers you the possibility of launching a custom
- command everytime it processes a Tick File.
- When Mail Manager processes a Tick File it performs the following
- operations:
- - If there is a file to replace, MM deletes the file from the area
- - it copies the file into the directory specified as Area Path.
- - it inserts the description of the file inside the file comment.
- If you want to perform some other operations you could insert them
- inside a script and configure it as a Tick Command. The configured
- script will be launched immediatelly after the above three
- operations.
- Inside the Command string you can insert the following control
- characters:
- \n - NewLine
- \q - Quotations Marks (")
- %s - Sysop Name
- %a - Area Tag
- %p - Area Path
- %P - Area Alternate Path
- %u - Area User Flags
- %d - File Description
- %b - File Size in Bytes
- %n - Original File Name ( Only Name )
- %N - Original File Name ( with the complete Path )
- %m - Destination File Name ( Only Name )
- %M - Destination File Name ( with the complete Path )
- %r - File replaced ( Only Name )
- %R - File replaced ( with the complete Path )
- %o - Origin Node
- %f - From Node
-
- WARNINGS
- --------
- - You cannot use Mail Manager ARexx commands inside the script
- launched as Tick Command
- - Mail Manager checks the return code of the Tick Command. If it
- is not '0' the Tick file won't be processed any further.
-
- In the "Label" string gadget you have to insert a symbolic name
- associated to the Tick Command, all the rest of the system will
- refer to the Tick Command with this label.
- In the "Com" string gadget you have to insert the Tick Command
- itself.
-
-
- 1.2.3 Archivers
-
- Here you can insert all the archivers you plan to use for
- arcing/unarcing mail bundles on your system.
- In the "Label" string gadget you have to insert a symbolic name
- associated to the Archiver, all the rest of the system will
- refer to the Archiver with this label.
- In the "Arc" string gadget you have to insert the command to be
- executed for arcing mail. Mail Manager will automatically append
- the name of the bundle and the name of the packet to compress, in
- this order.
- In the "UnArc" string gadget you have to insert the command to be
- executed for unarcing mail. Mail Manager will automatically append
- the name of the bundle to UnPack. The bundle will be unarced in the
- configured WorkDir.
- During import Mail Manager is able to identify the kind of archiver
- used to create the bundle. The identification is based on a
- particular sequence of characters in the first bytes of the bundle:
- "ID" is the matching sequence of bytes and "ID Pos" is its position
- inside of the bundle. These are the ID and ID Pos of the most used
- archivers:
-
- ARCHIVER ID ID Pos
- -------- ------ ------
- LHA "-lh" 2
- LZX "LZX" 0
- ZOO "ZOO" 0
- ZIP "PK" 0
- ARC "" 0
-
-
-
-
- 1.3 Misc 2
-
- 1.3.1 Variables
-
- 1.3.1.1 Check Dupes
-
- With these two Cycle Gadgets you can configure the management of
- Dupe Messages and Tick Files.
-
- 1.3.1.1.1 Messages
-
- With this Cycle Gadget you can configure the management of Dupe
- Messages.
-
- Disabled - No Dupe Checking
- Keep - The Dupe Message is recognized as a Dupe but it
- is normally imported
- Route to Bad - The Dupe Message is recognized as a Dupe and
- imported in the configured BAD Messages area.
- The message will be flagged as 'Dupe'.
- Kill - The Dupe Message is recognized as a Dupe and it
- is not imported at all.
-
-
- 1.3.1.1.1 Ticks
-
- With this Cycle Gadget you can configure the management of Dupe
- Tick Files.
-
- Disabled - No Dupe Checking
- Keep - The Dupe File is recognized as a Dupe. The old
- file is moved to the configured BackUp directory
- and the new file is normally imported.
- Route to Bad - The Dupe File is recognized as a Dupe and
- imported in the configured Bad Dir.
- Kill - The Dupe File is recognized as a Dupe and it is
- not imported at all.
-
-
-
- 1.3.1.2 Areas List
-
- With these two Cycle Gadgets you can configure the default status
- of the corresponding Cycle Gadgets of the Areas Window of Mail
- Manager:
-
- 1.3.1.2.1 Show
-
- This Cycle gadget configures the default type of areas that will
- be showed in the Areas List of the Areas Window of Mail Manager.
-
- All - Shows all the areas.
- Tot - Shows only areas which contain messages.
- New - Shows only areas which contain UnRead messages.
- Sys - Shows only areas which contain UnRead messages addressed
- to you.
- Unr - Shows only areas which contain UnReplied messages
- addressed to you.
- Imp - Shows only areas which contain messages imported during
- the last import.
- Echo - Shows only EchoMail areas
- Mail - Shows only NetMail areas
-
-
- 1.3.1.2.2 Order
-
- This Cycle gadget configures the default sorting method used in
- the Areas List of the Areas Window of Mail Manager:
-
- Configuration - Sorts areas in the same order as they are
- described in the configuration file.
- Alphabetic - Sorts areas in alphabetical order of their name
- Groups - Sorts areas in alphabetical order of their group
- Number Tot - Sorts areas by the total number of messages
- contained in the area
- Number New - Sorts areas by the number of UnRead messages
- contained in the area
- Number Sys - Sorts areas by the number of UnRead messages
- addressed to you contained in the area
- Number Unr - Sorts areas by the number of UnReplied messages
- addressed to you contained in the area
- Number Imp - Sorts areas by the number of messages imported
- during the last import
-
-
-
- 1.3.1.3 PreParse Strings
-
- In these two string gadgets you can insert a string that will be
- placed in front of every Kludge and Quoted line while you are
- reading a message. In the string you can include the following
- control characters:
-
- \b = Bold
- \i = Italic
- \u = Underline
- \n = Back to Plain
- \<n> = Use pen number <n> (1..9). You can configure the
- colors associated to these pens from the 'Palette'
- window of the Edit Screens part of MUIPrefs.
-
- 1.3.1.3.1 Kludges
-
- Here you can insert the string that will be placed in front of
- every Kludge line.
-
- 1.3.1.3.2 Quoted
-
- Here you can insert the string that will be placed in front of
- every Quoted line.
-
-
-
- 1.3.1.4 Delete Char
-
- In this string gadget you can insert the control character that
- will be inserted in front of the Bundle name before adding it to
- a Flow File. This will configure the management of the Bundle
- after it has been sent by your mailer:
-
- # ... Truncate the bundle to zero length
- ^ ... Delete the bundle (with logging)
- - ... Delete the bundle (without logging)
-
-
-
- 1.3.1.5 Switches
-
- 1.3.1.5.1 5D Origins
-
- If you set this CheckMark, the address inserted by Mail Manager
- at the end of the Origin line will include the domain.
-
-
- 1.3.1.5.2 Check Domains
-
- If you set this CheckMark, Mail Manager will work in a full 5D
- environment. In a full 5D environment, 2:335/602.2@fidonet is
- completely different from 2:335/602.2@amiganet.
- This gadget should always be selected; unselect it only if you
- are connected to someone that is unable to use the right domains.
-
-
- 1.3.1.5.3 Crunch Matrix
-
- If you set this CheckMark, NetMail for your Points will be
- crunched with the configured archiver. The format of netmail
- packets for all the other nodes is configured by the routing
- parameter.
- Of course this is only useful if you are a full node.
-
-
- 1.3.1.5.4 Do Backup
-
- If you set this CheckMark, Mail Manager will make a copy of the
- incoming bundles and PKTs in the Backup Dir before starting the
- Import function.
-
-
- 1.3.1.5.5 Keep Matrix
-
- By default, intransit messages ( Imported messages not addressed
- to one of your Addresses or Akas ), are flagged as 'DEL' as soon
- as Mail Manager has exported them. If you also want to keep
- intransit messages you have to set this CheckMark.
- Of course this is only useful if you are a full node.
-
-
- 1.3.1.5.6 Keep Sysop
-
- If you set this CheckMark, messages written or addressed to you
- won't be deleted by the Mail Manager Delete Function. Of course
- you can still delete them by setting the 'DEL' flag from inside
- Mail Manager.
-
-
- 1.3.1.5.7 Pack Every Bundle
-
- If you set this CheckMark, Mail Manager will archive exported
- Packets at the end of every imported bundle, otherwise it will
- archive the exported Packets at the end of the Import function.
-
-
- 1.3.1.5.8 Quote Kludges
-
- This CheckMark sets the default status of the Quote Kludges
- item of the Environment menu in the Browse window.
-
-
- 1.3.1.5.9 Reflow Messages
-
- This CheckMark sets the default status of the Reflow Gadget in
- the Message Parameters Window.
-
-
- 1.3.1.5.10 Safe Import
-
- If you set this CheckMark, Mail Manager will delete an incoming
- Bundle only after it has imported all the contained packets.
- You are advised to enable this option if you have assigned the
- Working Dir to somewhere in RAM:. This prevents you from losing
- messages in case of a crash during import.
-
-
- 1.3.1.5.11 Show Kludges
-
- This CheckMark sets the default status of the Show Kludges item
- of the Environment menu in the Browse window.
-
-
- 1.3.1.5.12 Show PassThrough
-
- If you set this CheckMark, PassThrough Areas will be visible in
- the Areas List of the Areas Window.
-
-
- 1.3.1.5.13 Smart Export
-
- If you set this CheckMark then, when you click on the Export
- Gadget of the Areas window and there is no Area Selected, Mail
- Manager will Export only areas flagged with the 'E' flag.
-
-
- 1.3.1.5.14 Threads Opened
-
- This CheckMark sets the default status of the Threads Window.
-
-
- 1.3.1.5.15 Text Styles
-
- This CheckMark sets the default status of the Text Styles item
- of the Environment menu in the Browse window.
-
-
-
- 1.3.2 Paths
-
- 1.3.2.1 Editor
-
- In this string gadget you should insert the editor command that
- will be executed by Mail Manager to edit a message. Put a `%s' in
- this command string to specify where Mail Manager should insert
- the name of the temporary file.
- The Editor should be runned in a synchronous way ( it should not
- return until you close it ). For example, with CED you should use
- "CED %s -sticky".
-
-
- 1.3.2.2 Archive File
-
- In this string gadget you can insert the default name of the file
- where Mail Manager will save a Message when you archive it.
- You can use the same control characters used for the Prologue Text.
-
-
- 1.3.2.3 Inbound Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will look for incoming Bundles, Packets and
- Files. It should be the same directory configured in your mailer
- as Inbound.
-
-
- 1.3.2.4 Outbound Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will place outgoing Packets and Flow Files. It
- should be the same directory configured in your mailer as Outbound.
-
-
- 1.3.2.5 Bad Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will move wrong or corrupted incoming Packets
- and Tick files.
-
-
- 1.3.2.6 Bundle Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will place outgoing Bundles. You can also use
- the same directory used for the Outbound Dir.
-
-
- 1.3.2.7 Backup Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will copy incoming Bundles and Packets before
- the Import function ( only if you have specified 'Do BackUp' ).
-
-
- 1.3.2.8 Tic Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will place outgoing .TIC files. You can also
- use the same directory used for the Outbound Dir.
-
-
- 1.3.2.9 Working Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will UnArc incoming Bundles before the Import.
-
-
- 1.3.2.10 Temp Pkt Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will create temporary Packets during the Export
- operation.
- It should be different from the Inbound and Working directories.
-
-
- 1.3.2.11 Nodelist Dir
-
- In this string gadget you can insert the name of the directory
- where Mail Manager will look for the compiled Nodelist.
-
-
- 1.3.2.12 Mail Device
-
- In this string gadget you can insert the name of the directory
- that Mail Manager will monitor in order to show you the available
- disk space. It should be the directory or device where you place
- your Message Base.
-
-
- 1.3.2.13 Userlist
-
- In this string gadget you can insert the name of the Userlist.
- Mail Manager uses the following userlist format:
-
- "<Full Name>" <5D Address> <nickname>
-
- for example:
-
- "Pino Aliberti" 2:335/602.2@fidonet pino
-
-
- 1.3.2.14 Statistics
-
- In this string gadget you can insert the name of the Statistics
- file. Mail Manager uses this file to store some useful
- information about the status of the messages areas.
-
-
-
- 1.3.3 Sizes
-
- 1.3.3.1 Task Priority
-
- This is the Task Priority of the Mail Manager task.
-
-
- 1.3.3.2 Min Free Mem
-
- If your available free memory is less than this value, Mail Manager
- will free some area buffers before scanning an area.
-
-
- 1.3.3.3 Max Pkt Size
-
- This is the rough maximum size of a Packet created during Export.
- The size of the Packet is checked before adding a message. If the
- size of the Packet is bigger than this value, the message will be
- added to a new Packet.
-
-
- 1.3.3.4 Max Bundle Size
-
- This is the very rough maximum size of a Bundle created during
- Export. The size of the Bundle is checked before adding a packet.
- If the size of the Bundle is bigger than this value, the packet
- will be added to a new Bundle.
-
-
- 1.3.3.5 Commands Stack
-
- This is the StackSize used for running external commands
- ( Archivers, Text Editor, Custom Commands and Tick Commands ).
-
-
-
- 1.3.4 Logs
-
- 1.3.4.1 Window
-
- This is the window used by Mail Manager to show you a log of the
- current Mail Manager session and functions as standard I/O window
- to run external commands.
- The 'Lev' slider gadget defines Mail Manager's verbosity during
- writes to the Log Window.
-
-
- 1.3.4.2 File
-
- This is the name of the Log File written by Mail Manager.
- The 'Lev' slider gadget defines Mail Manager's verbosity during
- writes to the Log File.
-
-
-
-
- 1.4 Texts
-
- 1.4.1 Prologues
-
- Here you can insert the Prologues you want to use in the Messages
- Areas. The Prologue is a phrase that Mail Manager inserts in the
- head of your reply to a message.
- The entry labeled as <Default> is the Default Prologue, it will be
- used in all the areas where you have not specified a particular
- Prologue.
- In the "Label" string gadget you will have to insert a symbolic name
- associated to the Prologue, all the rest of the system will refer to
- the Prologue with this label.
- In the "Prologue" string gadget you will have to insert the Prologue
- itself.
- In the phrase you can insert the following control characters:
-
- \n - NewLine
- \q - Quotations Marks (")
- \% - Percentage char (%)
-
- %F - Name of the Sender (Name and SurName)
- %f - Name of the Sender (Name)
- %K - Address of the Sender ( without Domain )
- %k - Address of the Sender ( without Point and Domain )
- %T - Name of the Addressee (Name and SurName)
- %t - Name of the Addressee(Name)
- %S - Subject of the message (Complete)
- %s - Subject of the message (First 20 characters)
- %D - Date and Time of the message
- %d - Date of the message
- %X - Current Date and Time
- %x - Current Date
- %Y - Sysop Name (Name and Surname)
- %a - Tag Name of the area
- %p - Path of the area
- %n - Number of the message
-
- If %F, %f, %T or %t are followed by some text enclosed in two `~'s
- this text will be used if the message was directed to or written by
- yourself. For example: "Look what %F~I~ wrote to %T~me~:"
-
-
- 1.4.2 Logos
-
- Here you can insert the Logos you want to use in the Messages Areas.
- The Logo is a signature that Mail Manager adds to the end of every
- message you write.
- The entry labeled as <Default> is the Default Logo, it will be used
- in all the areas where you have not specified a particular Logo.
- In the "Label" string gadget you will have to insert a symbolic name
- associated to the Logo, all the rest of the system will refer to the
- Logo with this label.
- In the "Logo" string gadget you will have to insert the Logo itself.
- In the phrase you can insert the same control characters described
- for Prologues.
-
-
- 1.4.3 Origins
-
- Here you can insert the Origins you want to use in the Messages
- Areas.
- The entry labeled as <Default> is the Default Origin, it will be
- used in all the areas where you have not specified a particular
- Origin.
- In the "Label" string gadget you will have to insert a symbolic name
- associated to the Origin, all the rest of the system will refer to
- the Origin with this label.
- In the "Origin" string gadget you have to insert the Origin itself.
-
-
- 1.4.4 Forward
-
- In the "Forward" string gadget you have to insert the phrase that
- Mail Manager inserts in the head of a forwarded message.
- In the phrase you can insert the same control characters described
- for Prologues.
-
-
-
-
- 1.5 Custom
-
- 1.5.1 Areas/Messages Commands
-
- Here you can configure up to 32 custom commands associated with
- the User Menu of the Areas and Messages windows.
- In the "Label" string gadget you will have to insert the name of the
- command, this string will be showed in the menu.
- In the "ShortCut" string gadget you can insert a character that will
- be used as ShortCut for calling the command. Of course you cannot
- use a character already used for another menu item of the same
- window.
- In the "Command" string gadget you will have to insert the command
- itself. Mail Manager will launch the command using the AmigaDOS
- 'Run' command, so you can also configure a command like:
- ">nil: BIN:Trapdoor call 2:335/602".
-
-
- 1.5.2 Browse Commands
-
- Here you can configure up to 32 custom commands associated to with
- the User Menu of the Browse window.
- In the "Label" string gadget you will have to insert the name of the
- command, this string will be showed in the menu.
- In the "ShortCut" string gadget you can insert a character that will
- be used as ShortCut for calling the command. Of course you cannot
- use a character already used for another menu item of the same
- window.
- In the "Command" string gadget you will have to insert the command
- itself. Mail Manager will launch the command using the AmigaDOS
- 'Run' command. In the string you can insert the same control
- characters described for Prologues, so a command like:
- "BIN:Trapdoor call %k" will make Trapdoor call the originating node
- of the message you are currently reading.
-
-
-
-
- 1.6 Nodes
-
- Here you can insert all the systems that normally exchange mail with
- you. If you are a point this is the place where you should configure
- all your bosses. If you are a node this is the place where you
- should configure all the points and nodes which exchange mail with
- your system.
-
-
- 1.6.1 Packets
-
- 1.6.1.1 Archivers
-
- Here you can select the archiver that will be used to crunch the
- mail packets addressed to the selected system.
- The system could send you mail packets crunched with any of the
- configured archivers, Mail Manager is able to identify the archiver
- used to create the bundle.
-
-
- 1.6.1.2 Packets
-
- Here you can configure the format of the Mail Packets addressed to
- the selected system and the format of Seen-By and Path lines
- inserted in the packets.
- Mail Manager uses the standards described in FTS-0001 for 3D
- packets, in FSC-0048 for 4D packets and in FSC-0045 for 5D packets.
-
-
- 1.6.1.3 Flavors
-
- Here you can configure the method used to send EchoMail Packets and
- Tick Files to the selected system.
- Packets or Tick Files will never be created for a VIRTUAL system.
-
-
- 1.6.1.4 Passwords
-
- Here you can configure the passwords used with the selected system.
-
- Packet - Password used/expected for Packets
- Tick - Password used/expected for Tick Files
- AreaFix - Password expected for AreaFix Messages
-
-
-
- 1.6.2 Groups
-
- From here you can link/unlink the selected system to/from the
- defined groups. This is only really useful for full nodes which will
- mostly use this function for AreaFix.
-
-
-
- 1.6.3 Areas
-
- From here you can link/unlink the selected system to/from the
- defined EchoMail and Tick Areas.
-
-
-
- 1.6.4 Misc
-
- 1.6.4.1 UserFlags
-
- In this string gadget you can insert every kind of information
- about the selected system. Mail Manager does not use this field,
- but it could be read from ARexx so you could use it to store useful
- information for ARexx scripts. Another possible use is to remember
- the name of the sysop of the selected system.
-
-
- 1.6.4.2 Can Create Areas
-
- If you set this CheckMark, the selected system will be able to
- automatically create new EchoMail areas on your system. The new
- areas will be created following the values configured in the
- Auto-Created Area Default gadgets.
-
-
-
-
- 1.7 Routing
-
- The Routing is the heart of NetMail handling. By configuring the
- Routing you tell Mail Manager how and to which system it has to route
- NetMails to. This is normally used to get the message to reach it's
- final destination via the shortest route.
- When Mail Manager exports a NetMail Message it reads the origin and
- destination addresses and:
- - If the destination address is one of your Addresses or Akas, MM
- flags the message as Sent, updates some kludges and stops the
- message.
- - If the origin address is one of your Addresses or Akas and it is
- flagged as Hold or as Crash, MM inserts it in an outgoing packet
- for the destination node with the proper flavor.
- - If you are a node and the destination address is one of your listed
- points, MM inserts the message in an outgoing packet for the point
- with the flavor specified for the point.
- - In all the other cases it follows the Routing statements. It scans
- the statements from the first to the last ( so order is important )
- and as soon as it finds a statement that matches with the
- destination address of the message and with its flavor it performs
- the configured action.
-
-
- 1.7.1 Settings
-
- Here you can insert all the Routing statements. Be careful, all the
- possible addresses must be covered.
-
- 1.7.1.1 Original Message
-
- In the Pattern string gadget you can insert the Address Pattern
- that must be satisfied by the destination address of the message
- in order to perform the corresponding Action.
- You have to enter the Address Pattern in 5D format
- ( <zone>:<net>/<node>.<point>@<domain> ). In every field of the
- pattern you can use every AmigaDos wilcard.
- Here are some examples:
-
- *:*/*.*@fidonet - all the msgs addressed to a fidonet node
- *:*/*.*@amiganet - all the msgs addressed to an amiganet node
- [1-6]:*/*.*@* - all the msgs addressed to zones 1 thru 6
- ((39)|(40)):*/*.*@* - all the msgs addressed to zones 39 and 40
- *:*/*.*@* - all the msgs
-
- The Flavor cycle gadget defines the Flavor that the message must
- own in order to perform the corresponding Action.
-
-
- 1.7.1.2 Action
-
- SEND - Sends the message uncompressed
- ARCHIVE - Sends the message compressed
-
-
- 1.7.1.3 To
-
- Here you can select the Node where you want to route all the
- messages that satisfy the Pattern. You can also define the Flavor
- used for routing the message.
-
-
-
- 1.7.2 Test
-
- Here you can test your Routing statements.
-
-
-
-
- 1.8 Areas
-
- 1.8.1 Messages
-
- Here you can insert all the Messages Areas you want to manage on
- your system.
- In the Tag string gadget you can insert the TAG-name of the area.
- You cannot use the same TAG-name for two different Messages Areas.
- Normally this won't happen with EchoMail areas, but you also have to
- name your NetMail Areas with different TAG-names, e.g. MATRIX.FIDO
- or NETMAIL.AMY.
- The Type cycle gadget defines the type of the Area. Mail Manager
- supports four different types of Messages Areas:
-
- MAIL - NetMail (Matrix) Area. You can configure a single or
- multiple NetMail Areas. Even if you are connected to
- multiple domains/nodes, Mail Manager is able to manage
- all the Netmail messages with a single NetMail Area.
- Anyway, if you prefer, you can configure a different
- NetMail Area for every domain/node you are connected to.
-
- ECHO - Standard EchoMail Area.
-
- FILE ECHO - EchoMail Area with File Attached Management. Mail
- Manager is able to manage attached files in EchoMail
- areas. Be careful, File Attaches in EchoMail areas is
- only supported by a few programs and it is not legal to
- send them in normal EchoMail areas.
- Configure an EchoMail Area as a File Echo only if you
- are sure that File Attaches are allowed in that area.
-
- BAD - Bad Area. You have to configure one and only one Bad
- Area.
-
-
- 1.8.1.1 System
-
- 1.8.1.1.1 Name
-
- In this string gadget you can insert the Area Name that Mail
- Manager will show you in the Areas List of the Areas Window. You
- can also use the same control characters used for the PreParse
- Strings. This is a compulsory field.
-
-
- 1.8.1.1.2 Desc
-
- In this string gadget you can insert a long description for the
- Area. Mail Manager does not use this field, but it could be read
- from ARexx, normally a Full Node will insert a string here which
- will be returned as Area Description by AreaFix.
-
-
- 1.8.1.1.3 Path
-
- In this string gadget you can insert the path of the Primary Area
- Directory. This is the directory where Mail Manager will store
- the Message Base of the Area. This is a compulsory field.
-
-
- 1.8.1.1.4 AltPath
-
- In this string gadget you can insert the path of the Alternate
- Area Directory. Mail Manager normally uses this directory to
- store File Attaches in NetMail and File Echo Areas. If you do
- not specify an Alternate Area Directory Mail Manager will store
- File Attaches in the Primary Area Directory.
-
-
- 1.8.1.1.5 UserFlags
-
- In this string gadget you can insert every kind of information
- about the Area. Mail Manager does not use this field, but it
- could be read from ARexx so you could use it to store useful
- information for ARexx scripts.
-
-
- 1.8.1.1.6 Address
-
- Here you can select the Address you want to use in the Area.
- In EchoMail Areas this will be the address inserted in the Origin
- line.
- In NetMail Areas this will be the address inserted by default in
- the From Address string gadget of the Message parameters Window
- when you write a message. Normally you don't have to worry about
- the contents of this gadget, During the export operation Mail
- Manager will scan the configured Addresses ( Akas won't be
- scanned ) and will automatically choose the right one ( normally
- the nearest to the destination address ).
-
-
- 1.8.1.1.7 Group
-
- Here you can select the group the area belongs to and the access
- level required for the area. This is only really useful for Full
- Nodes which use this information mainly for AreaFix. Anyway, a
- simple Point could use this to group together some areas with the
- same characteristics. If you do not need Groups, you can define a
- single group and link all the areas to this group.
-
-
-
- 1.8.1.2 Nodes
-
- From here you can link/unlink the configured Nodes to/from the
- selected Area.
-
-
-
- 1.8.1.3 Texts
-
- Here you can select the Sysop name, the Prologue, the Logo and the
- Origin you want to use in the Area.
-
-
-
- 1.8.1.4 Misc
-
- 1.8.1.4.1 Read Only
-
- If you set this CheckMark you cannot write messages in this area.
-
-
- 1.8.1.4.2 Two pass Import
-
- If you set this CheckMark, messages imported in this Area won't
- be automatically exported during the Import operation. You will
- have to launch the Export operation on the area after the Import.
- This is useful if you want to perform some additional operations
- on imported messages before exporting them. Normally Full Nodes
- will have to set their Netmail Areas as 'Two Pass Import' in
- order to process the imported messages with their AreaFix and
- Message Tracker scripts before exporting the messages.
-
-
- 1.8.1.4.3 CharSet
-
- Here you can configure the CharSets used in the Area.
- The Read cycle gadget defines the default Charset assumed for
- messages without a CHRS kludge.
- The Write cycle gadget defines the Charset used for reading and
- writing messages.
-
-
- 1.8.1.4.4 Delete By
-
- Here you can define the method used for the Delete operation and
- the minimum number of messages left in the Area after a Delete
- operation.
-
-
- 1.8.1.4.5 Font
-
- Here you can select the Font used when reading messages in this
- Area.
-
-
- 1.8.1.4.6 Msgbase
-
- Here you can select the type of Message Base used for the Area.
-
- Plain - This is the standard Fidonet message base. One file
- for every message. Really really slow, almost
- useless, but it is the standard.
- Indexed - Stores the messages in the same format of the Plain
- message base, but it also keeps an index of all the
- messages in the area. This speeds things really up
- and, at the same time, adheres to the standards.
- Quick - Only two files per area, one with all the messages
- and one with an index. Really really fast.
- Compressed - Same format as the Quick message base, but the body
- of the messages is compressed. The compression rate
- is about 30%, but on fast machines it is faster than
- the Quick message base !!!
-
- The Plain and Indexed message bases can be shared with other
- programs.
-
-
- 1.8.1.4.7 Show
-
- Here you can configure the initial state of the Show cycle gadget
- of the Area.
-
-
- 1.8.1.4.8 Sort
-
- Here you can configure the initial state of the Sort cycle gadget
- of the Area.
-
-
-
- 1.8.2 Ticks
-
- Here you can insert all the Tick Areas you want to manage on your
- system.
- In the Tag string gadget you can insert the TAG-name of the area.
- You cannot use the same TAG-name for two different Tick Areas.
-
-
- 1.8.2.1 System
-
- 1.8.2.1.1 Desc
-
- In this string gadget you can insert a long description for the
- Area. Mail Manager does not use this field, but it could be read
- from ARexx. Normally Full Nodes will insert a string here which
- will be returned as Area Description by AreaFix.
-
-
- 1.8.2.1.2 Path
-
- In this string gadget you can insert the path of the Primary Area
- Directory. This is the directory where Mail Manager will store
- the Tick Files hatched in the Area. This is a compulsory field.
-
-
- 1.8.2.1.3 AltPath
-
- In this string gadget you can insert the path of the Alternate
- Area Directory. Mail Manager does not use this field, but it
- could be read from ARexx.
-
-
- 1.8.2.1.4 UserFlags
-
- In this string gadget you can insert every kind of information
- about the Area. Mail Manager does not use this field, but it
- could be read from ARexx so you could use it to store useful
- information for ARexx scripts.
-
-
- 1.8.2.1.5 Address
-
- Here you can select the Address you want to use in the Area.
-
-
- 1.8.2.1.6 Group
-
- Here you can select the group the area belongs to and the access
- level required for the area. This is only really useful for Full
- Nodes which use this information mainly for AreaFix. Anyway, a
- simple Point could use this to group together some areas with the
- same characteristics. If you do not need Groups, you can define a
- single group and link all the areas to this group.
-
-
-
- 1.8.2.2 Nodes
-
- From here you can link/unlink the configured Nodes to/from the
- selected Area.
-
-
-
- 1.8.2.3 Tick Commands
-
- Here you can select the Tick Command you want to use in the Area.
-
-
-
-
-
-
-
- 2 MAIL MANAGER GRAPHICAL USER INTERFACE
-
- Mail Manager Graphical User Interface deeply uses the features of MUI.
- With MUI you can configure almost everything of the Mail Manager GUI,
- besides you can control everything with the mouse or even with the
- keyboard. In order to completelly exploit such a powerful interface you
- SHOULD read MUI's documentation carefully.
-
-
- 2.1 Areas Window
-
-
- 2.1.1 Areas List
-
- Here MM shows some information about the areas:
-
- AreaName - Is the name of the area
- Tot - Is the total number of messages present in the area
- New - Is the number of UnRead messages in the area
- Sys - Is the number of UnRead messages addressed to you in the
- area
- Unr - Is the number of UnReplied messages addressed to you in
- the area
- Imp - Is the number of messages tossed into the area during the
- last import
- HiMsg - Is the number of the last message in the Area
- Type - Is the type of the area ( Mail / Echo / FEcho / Bad )
- MBase - Is the type of message base used in the area
- ( PThro / Plain / Idx / Quick / Comp )
- NDel - Is the minimum number of messages left by MM after a
- Delete operation
- Flags - Here MM shows some other information
- 1 flag : Sorting method used for the delete operation
- ( N=Number D=Date )
- 2 flag : Sorting method used in the Messages Window
- ( N=Number D=Date F=From T=To S=Subject )
- 3 flag : Read Only Flag ( R=Read Only area)
- 4 flag : Area Status ( S=Scanned )
- 5 flag : Export Flag ( E=Area contains UnSent messages )
-
- You can 100% rely on this information only if you have just scanned
- the area.
-
- If you single click on an area, you select that area, if you double
- click on an area, you will enter in that area. Of course you can use
- all the configured keyboard shortcuts for a MUI listview.
-
-
-
- 2.1.2 Areas Management
-
-
- 2.1.2.1 All
-
- Selects All the areas showed in the Areas List.
-
-
-
- 2.1.2.2 None
-
- UnSelects All the selected areas showed in the Areas List.
-
-
-
- 2.1.2.3 Import
-
- Launches the Import function.
-
- MM looks in your inbound directory for mail packets and bundles.
-
- If you have set 'Do BackUp' it makes also a copy of packets and
- bundles in the configured BackUp Directory.
-
- In case of bundles, MM recognizes the used archiver and
- automatically unpacks the bundles in the configured Work Directory.
-
- Then MM reads the message from the packet, exports it and tosses
- it into the appropriate echo or mail area. If you do not want to
- simultaneously import and export a message ( for example if you
- want to launch a filter or a msgtracker before exporting a just
- imported message ) you have to set 'TwoPassImport' for the area.
-
- Before and after every import operation MM tries to rescue
- Temporary Flow files and Orphan Packets. Temporary Flow files are
- generated when the main Flow file for a node is locked and MM
- cannot write in it. Orphan Packets are normally generated when a
- guru happens while MM is performing an Import/Export Operation.
-
-
-
- 2.1.2.4 Export
-
- Launches the Export function.
- If there are any selected areas, MM will only process those areas,
- otherwise it will process all the areas or, if you have set
- 'Smart Export', only areas with UnSent messages.
-
- MM looks into the areas for UnSent messages. When it finds one it
- behaves differently if the area is a NetMail one or an EchoMail
- one.
-
- In case of a NetMail area, it reads the origin and destination
- addresses and:
- - If the destination address is one of your Addresses or Akas, MM
- flags the message as Sent, updates some kludges and stops the
- message.
- - If the origin address is one of your Addresses or Akas and it
- is flagged as Hold or as Crash, MM inserts it in an outgoing
- packet for the destination node with the proper flavor.
- - If you are a node and the destination address is one of your
- listed points, MM inserts the message in an outgoing packet for
- the point with the flavor specified for the point.
- - In all the other cases it follows the Routing statements.
-
- In case of an EchoMail area, it parses the Seen-By lines and
- inserts the message into an outgoing packet for every node linked
- to the area that is not already listed in the Seen-By lines. The
- flavor of the packet will be the one you have specified in the
- corresponding Node configuration. MM never sends the message back
- to the node that has sent it to you, even if the node is not
- listed in the Seen-By lines.
-
-
- During the export operation MM also manages File Attaches. MM is
- able to manage both NetMail and EchoMail file attached:
-
- NetMail file attaches are managed only if one or more of the
- following conditions are satisfied:
- - The origin or the destination address of the message is one of
- your Addresses/Akas.
- - The destination address of the message is one of your listed
- points
- - The origin and destination addresses of the message are both
- listed on your system.
-
- EchoMail file attached are managed only if you have configured the
- area as 'File Echo'.
-
- When MM manages file attaches, it makes a copy of the file into
- the directory you have specified as 'AltPath' for the area ( or in
- the area directory if you have not specified an 'AltPath' ), and
- then inserts its filename into the flow file for the destination
- node(s). If the origin address of the message is not one of your
- Addresses/Akas, the file will be deleted from the Inbound dir.
- An attached file inherits its flavor from the message it is
- attached to.
-
-
-
- 2.1.2.5 Scan
-
- Launches the Scan function.
- If there are selected areas, MM scans only those areas, otherwise
- it scans all the areas.
-
- MM scans the message base looking for messages, building an index
- of the area in memory.
-
- MM supports four different types of message bases:
- Plain - This is the standard Fidonet message base. One file
- for every message. Really really slow, almost
- useless, but it is the standard.
- Indexed - Stores the messages in the same format of the Plain
- message base, but it keeps also an index of all the
- messages in the area. This speeds things really up
- and, at the same time, keeps the standards.
- Quick - Only two files per area, one with all the messages
- and one with an index. Really really fast.
- Compressed - Same format of the Quick message base, but the body
- of the messages is compressed. The compression rate
- is about 30%, but on fast machines it is faster than
- the Quick message base !!!
-
-
- The Plain and Indexed message bases can be shared with other
- programs.
-
- When MM scans an area, it is able to understand if something has
- modified its message base. If the area index is already in memory
- the area will be scanned again only if it has been modified from
- an external program.
- Of course MM automatically performs a scan before executing every
- other operation on an area.
-
-
-
- 2.1.2.6 Free
-
- Launches the Free function.
- If there are selected areas, MM frees only those areas, otherwise
- it frees all the areas.
-
- Frees the memory used for keeping the index of a scanned area. If
- the message base of the area is not Plain it also writes the index
- on the disk.
- MM automatically tries to free some areas when it reaches the
- configured 'Min Free Mem' value.
- Of course Mail Manager automatically frees all the areas everytime
- you quit it.
-
-
-
- 2.1.2.7 Update
-
- Launches the Update function.
- If there are selected areas, MM updates only those areas,
- otherwise it updates all the areas.
-
- Writes on disk the index of the area, but continues to keep it in
- memory.
- Of course it is completelly useless on a Plain message base.
-
-
-
- 2.1.2.8 Optimize
-
- Launches the Optimize function on the selected areas.
-
- Optimizes the message base in Quick or Compressed areas.
- The Optimize function is automatically performed at the end of
- every Delete operation, anyway it is always a good idea to
- manually perform it once in a while.
- When you modify a message ( for example when you edit, delete or
- even export it ) in a Quick or Compressed area the disk space
- associated with the old version of the message won't be freed
- immediatelly. You will have to optimize the area in order to free
- the unused disk space and to reorganize the message base as
- efficiently as possible. It also renumbers the area.
- Of course this function is completelly useless on Plain and
- Indexed message bases.
-
-
-
- 2.1.2.9 Delete
-
- Launches the Delete function on the selected areas.
-
- Deletes messages from the area. It follows the DeleteBy settings
- for the area. You can protect a message from the deletion by
- setting the 'Protected' message flag.
- If you have set 'Keep Sysop', messages written or addressed to you
- won't be deleted.
-
-
-
- 2.1.2.10 Purge
-
- Launches the Purge function on the selected areas.
-
- Performs the same operations as the Delete function, but it does
- not delete UnRead messages.
-
-
-
- 2.1.2.11 Show
-
- This Cycle gadget selects the type of areas that will be showed in
- the Areas List.
-
- All - Shows all the areas.
- Tot - Shows only areas which contain messages.
- New - Shows only areas which contain UnRead messages.
- Sys - Shows only areas which contain UnRead messages addressed to
- you.
- Unr - Shows only areas which contain UnReplied messages addressed
- to you.
- Imp - Shows only areas which contain messages imported during the
- last import.
- Echo - Shows only EchoMail areas
- Mail - Shows only NetMail areas
-
- You can configure the initial state of this gadget with the
- Areas List 'Show' configuration parameter.
-
- Remember that also the status of the Domains menu could affect
- the number of areas showed in the Areas List.
-
-
-
- 2.1.2.12 Sort
-
- This Cycle gadget selects the sorting method used in the Areas
- List.
-
- Config - Sorts areas in the same order as they are described
- in the configuration file.
- Alphabetic - Sorts areas in alphabetical order of their name
- Groups - Sorts areas in alphabetical order of their group
- Number Tot - Sorts areas by the total number of messages
- contained in the area
- Number New - Sorts areas by the number of UnRead messages
- contained in the area
- Number Sys - Sorts areas by the number of UnRead messages
- addressed to you contained in the area
- Number Unr - Sorts areas by the number of UnReplied messages
- addressed to you contained in the area
- Number Imp - Sorts areas by the number of messages imported
- during the last import
-
- You can configure the initial state of this gadget with the
- Areas List 'Order' parameter.
-
-
-
-
-
- 2.1.3 Areas Menus
-
-
- 2.1.3.1 Project
-
-
- 2.1.3.1.1 About
-
- Shows some information about Mail Manager.
-
-
-
- 2.1.3.1.1 Quit
-
- Quits Mail Manager.
- You can also quit Mail Manager by closing the Areas Window ( MUI
- allows you to configure a shortcut also for closing a window ).
- In this last case Mail Manager will open a requester asking you
- to confirm the operation.
-
-
-
-
-
- 2.1.3.2 Configuration
-
-
- 2.1.3.2.1 Edit
-
- Calls MM_Prefs allowing you to edit your actual Mail Manager
- configuration. MM_Prefs should be located in MM:Bin/.
-
-
-
- 2.1.3.2.2 Load...
-
- Opens a file requester allowing you to select a particular
- configuration file to load.
-
-
-
- 2.1.3.2.3 Save
-
- Saves the actual configuration with the same file name it has
- been loaded.
-
-
-
- 2.1.3.2.4 Save As...
-
- Opens a file requester allowing you to select the file name with
- which the actual configuration will be saved.
-
-
-
-
-
- 2.1.3.3 Ticks
-
-
- 2.1.3.3.1 Import
-
- Launches the Ticks Import function.
-
- MM looks in your inbound directory for .TIC files.
- Then MM reads and parses them. If everything is OK it imports the
- corresponding file. Mail Manager performs the following
- operations:
- - If there is a file to replace, MM deletes the file from the area
- - it copies the file into the directory specified as Area Path.
- - it inserts the description of the file inside the file comment.
- Then if you have configured a TickCommand for the Area, MM will
- launch the configured command.
- If everything is OK it will export the Tick file to the linked
- nodes and will delete the .Tic and the associated file from the
- Inbound dir.
-
-
-
- 2.1.3.3.2 Hatch
-
- Allows you to insert a file into a Tick Area.
- When you press the OK gadget it will launch the following
- operations:
- - If there is a file to replace, MM deletes the file from the area
- - it copies the file into the directory specified as Area Path.
- - it inserts the description of the file inside the file comment.
- Then if you have configured a TickCommand for the Area, MM will
- launch the configured command.
- If everything is OK it will export the Tick file to the linked
- nodes.
-
-
-
-
-
- 2.1.3.4 Miscellaneous
-
-
- 2.1.3.4.1 File Request
-
- Opens the MM File Request window. In the Node gadget you can
- enter the node address from which you would like to request the
- files. If the node is listed on your system you can also select
- it from the associated popup. Then you can enter the filenames
- in the string gadget below the listview.
- To delete a file just select it from the listview, clear the
- string gadget and press enter.
- If a requested file is already present in the .REQ file, it
- won't be added again.
-
-
-
- 2.1.3.4.2 Area Statistics
-
- Displays some useful information about the selected areas.
-
-
-
- 2.1.3.4.3 Renumber
-
- Launches the Renumber function on the selected areas.
-
- It renumbers only areas in Plain or Indexed message bases; areas
- in Quick and Compressed message bases are automatically
- renumbered during the Optimize function.
- You have to renumber an area only if the message numbers are
- becoming really high ( the maximum message number allowed in
- Fidonet standards is 65535 ), otherwise there is no valid reason
- for renumbering an area.
- This function does not update the link fields of the message
- header. This field is set by MM during import, but MM itself
- does not really use it. Nevertheless it is used from other
- programs, for example from DLG, so DLG users should renumber
- their message bases only with the DLG internal Renumber
- function.
-
-
-
- 2.1.3.4.4 Convert Message Base
-
- Converts the Message Base of an area from one type to another.
-
-
-
- 2.1.3.4.5 Deep Scan
-
- Launches the Deep Scan function on the selected areas.
-
- Performs the same operations of the Scan function, but it
- ignores the indexes written on disk. It is really much slower
- than the Scan operation, and it is useful only if you think that
- there is something wrong in the index file.
- MM automatically switches from Scan to Deep Scan when it
- understands that the index file of an area is wrong ( for
- example when an external program has modified the message base,
- making the index outdated ).
- Of course it is completely useless on a Plain message base.
-
-
-
- 2.1.3.4.6 Write Stats
-
- Updates the statistics file.
- Mail Manager automatically updates the statistics file everytime
- you quit or iconify it.
-
-
-
- 2.1.3.4.7 Restore Bad
-
- Restores messages tossed into the bad area because the original
- area did not exist when they were imported (such messages are
- flagged as UNKNWAREA), or because the node is unknown or not
- linked to the area ( flagged as UNLNKNODE ). Of course messages
- flagged as UNKNWAREA will be restored only if, in the mean time,
- you have created the area.
-
-
-
-
-
- 2.1.3.5 Domains
-
- This menu lists all the domains you have configured.
- With this menu you can include or exclude from the areas list all
- the areas that belong to a particular domain.
-
-
-
-
-
- 2.1.3.6 User
-
- This menu lists all the user definable commands you have
- configured as Custom Areas Commands. When you select one of its
- items the associated command will be launched with the AmigaDOS
- 'Run' command.
-
-
-
-
-
-
- 2.2 Messages Window
-
-
- 2.2.1 Messages List
-
- Here MM shows some information about the messages in the area:
-
- Num - Is the number of the message
- Date - Is the creation date of the message
- From - Is the name of the sender of the message
- To - Is the name of the addressee of the message
- Subj - Is the subject of the message
- Flags - Here MM shows some other information
- 1 flag : (U) UnReplied flag. The message is UnReplied
- and addressed to you
- 2 flag : (S) Sysop flag. The message is UnRead and
- addressed to you
- 3 flag : (N) New flag. The message is UnRead
- 4 flag : (I) Imported flag. The message has been imported
- ( it has not been written on your system ).
- 5 flag : (S) Sent flag. The message has been exported.
- 6 flag : (M) Marked flag. Useful for flagging a message
- for you own purposes.
- 7 flag : (P) Protected flag. The message is protected
- from deletion.
- 8 flag : (D) Deleted flag. The message is flagged for
- deletion.
-
- If you single click on an message, you select that message, if you
- double click on an message, you will read that message. Of course
- you can use all the configured keyboard shortcuts for a MUI listview.
-
-
-
-
- 2.2.2 Messages Management
-
-
- 2.2.2.1 All
-
- Selects All the messages showed in the Messages List.
-
-
-
- 2.2.2.2 None
-
- UnSelects All the selected messages showed in the Messages List.
-
-
-
- 2.2.2.3 Search
-
- Opens the Search Messages window.
- You can insert a different search pattern ( All the AmigaDOS
- WildCard are allowed ) in every string gadget.
- The 'Case' cycle gadget allows you to choose if the Search will be
- case sensitive or insensitive, the 'Match' cycle gadget allows you
- to choose if the messages should simultaneously match all the
- entered patterns or if it enough to match a single pattern.
- When you press 'Ok' Mail Manager will select all the messages that
- satisfy the above conditions.
-
-
-
- 2.2.2.4 Flags
-
- Opens the Message Flags window.
- It allows you to set or clear the flags of the selected messages.
- It also allows you to select messages with a particular flag set.
-
-
-
- 2.2.2.5 R News
-
- Changes the Show cycle gadget status to 'New' and starts reading
- the first UnRead message.
-
-
-
- 2.2.2.6 R Slct
-
- Changes the Show cycle gadget status to 'Selected' and starts
- reading the first Selected message.
- Useful, for example, if you want to read all the messages
- selected with the Search or Flags functions.
-
-
-
- 2.2.2.7 Write
-
- Calls the configured Text Editor allowing you to write a new
- message in the current area. As soon as you close the editor it
- opens the Message Parameters Window allowing you to insert the
- Message Parameters.
-
-
-
- 2.2.2.8 Forward
-
- Allows you to forward the active message to another area. It
- opens a requester allowing you to select the area where you want
- to forward the message. It then calls the configured Text Editor
- allowing you to edit the message. As soon as you close the editor
- it opens the Message Parameters Window allowing you to edit the
- Message Parameters.
-
-
-
- 2.2.2.9 Edit
-
- Allows you to modify an existing message. It calls the configured
- Text Editor allowing you to edit the text of the active message.
- As soon as you close the editor it opens the Message Parameters
- Window allowing you to edit the Message Parameters.
-
-
-
- 2.2.2.10 Edit Hdr
-
- Allows you to modify the header of an existing message. It opens
- the Message Parameters Window allowing you to edit the parameters
- of the active message.
-
-
-
- 2.2.2.11 Reply
-
- Allows you to reply to the active message. It reformats and
- quotes the message, next it calls the configured Text Editor
- allowing you to type your reply.
- As soon as you close the editor it opens the Message Parameters
- Window allowing you to edit the Message Parameters.
-
-
-
- 2.2.2.12 X Reply
-
- Performs the same operations as the Reply function, but it opens a
- requester allowing you to select the area where you want to post
- your reply.
-
-
-
- 2.2.2.13 Show
-
- This Cycle gadget selects the type of messages that will be showed
- in the Messages List.
-
- All - Shows all the messages.
- New - Shows only UnRead messages.
- Sysop - Shows only UnRead messages addressed to you.
- UnRepl - Shows only UnReplied messages addressed to you.
- Last Imp - Shows only messages imported during the last import.
- Selected - Shows only selected messages.
-
- You can configure the initial state of this gadget with the
- Show parameter in the Messages Areas configuration.
-
-
-
- 2.2.2.14 Sort
-
- This Cycle gadget selects the sorting method used in the Messages
- List.
-
- Number - Sorts messages by their number
- Date - Sorts messages by their creation date
- From - Sorts messages by alphabetical order of their sender
- To - Sorts messages by alphabetical order of their addressee
- Subject - Sorts messages by alphabetical order of their subject
-
- You can configure the initial state of this gadget with the
- SortBy parameter in the Messages Areas configuration.
-
-
-
-
-
- 2.2.3 Messages Menus
-
-
- 2.2.3.1 Messages
-
-
- 2.2.3.1.1 Delete
-
- Toggles the status of the Deleted Flag of the selected messages.
-
-
-
- 2.2.3.1.2 Protect
-
- Toggles the status of the Protected Flag of the selected messages.
-
-
-
- 2.2.3.1.3 Mark
-
- Toggles the status of the Marked Flag of the selected messages.
-
-
-
- 2.2.3.1.4 Archive
-
- Opens a file requester allowing you to select the file where you
- want to save the selected messsages.
- You can configure the default name of the file with the
- 'Archive File' parameter.
-
-
-
- 2.2.3.1.5 Print
-
- Prints the selected messages on the configured printer.
-
-
-
- 2.2.3.1.6 Toggle UnReplied Flag
-
- Toggles the status of the UnReplied Flag of the selected messages.
-
-
-
-
- 2.2.3.2 Miscellaneous
-
-
- 2.2.3.2.1 File Request
-
- Opens the MM File Request window. In the Node gadget you can
- enter the node address from which you would like to request the
- files. If the node is listed on your system you can also select
- it from the associated popup. Then you can enter the file names
- in the string gadget below the listview.
- To delete a file just select it from the listview, clear the
- string gadget and press enter.
- If a requested file is already present in the .REQ file, it
- won't be added again.
-
-
-
- 2.2.3.2.2 Areas Window
-
- Goes Back to the Areas Window
-
-
-
- 2.2.3.2.3 Areas List
-
- Opens a requester allowing you to select the area where you want
- to go.
-
-
-
- 2.2.3.2.4 Previous Area
-
- Goes to the previous area.
-
-
-
- 2.2.3.2.5 Next Area
-
- Goes to the next area.
-
-
-
- 2.2.3.2.6 Previous UnRead Area
-
- Goes to the previous area with unread messages.
-
-
-
- 2.2.3.2.7 Next UnRead Area
-
- Goes to the next area with unread messages.
-
-
-
- 2.2.3.2.8 Export Area
-
- Performs an export of the current area.
-
-
-
-
- 2.2.3.3 User
-
- This is a copy of the User Menu of the Areas Window.
-
-
-
-
-
-
-
-
- 2.3 Browse Window
-
-
- 2.3.1 Browse Window Gadgets
-
-
- 2.3.1.1 Threads
-
- Opens the Threads window. In this window Mail Manager shows you
- the reply thread of the current message.
- Mail Manager has a really powerful reply thread management. It is
- able to link messages on Subject or on MSGID/REPLY kludges. You
- can change the type of linking with the cycle gadget below the
- listview. In the listview Mail Manager shows you all the messages
- that belong to the thread. For every message it shows the status
- of the New flag, the name of the Sender, the name of the Adrressee
- and the message number.
- The entry corresponding to the Current Message ( the message
- showed in the Browse window ) is the one with the ListView cursor
- on, while the entry corresponding to the Parent Message is the one
- showed in bold.
- The Parent Message is particularly important if you are linking
- messages on MSGID/REPLY kludges. It is the message on which the
- thread is based. The message preceding it is the message it is
- answering to, while all the messages following it are replies to
- it. If you single-click on an entry, Mail Manager will show you
- that message on the Browse window, but it does not change the
- Parent Message. If you double-click on an entry, Mail Manager
- will show you that message on the Browse window, and it makes it
- the Parent Message.
- For example consider the following reply thread:
-
- 1
- / \
- 2 3
- / / \
- 4 5 6
- /|\ \
- 7 8 9 10
-
- suppose you are reading message 3 and that it is also the Parent
- Message: the thread window will show you messages 1-3-5-6, the 3
- will be active and in bold. If you single-click on message 5,
- Mail Manager will show you that message in the Browse window while
- the threads listview will show you the same entries, but now the
- cursor will be on message 5. If instead you double-click on
- message 5, Mail Manager will show you that message in the Browse
- window, but now the threads listview will show you messages
- 3-5-7-8-9, with the 5 active and in bold.
-
-
-
- 2.3.1.2 Write
-
- Calls the configured Text Editor allowing you to write a new
- message in the current area. As soon as you close the editor it
- opens the Message Parameters Window allowing you to insert the
- Message Parameters.
-
-
-
- 2.3.1.3 Forward
-
- Allows you to forward the current message to another area. It
- opens a requester allowing you to select the area where you want
- to forward the message. It then calls the configured Text Editor
- allowing you to edit the message. As soon as you close the editor
- it opens the Message Parameters Window allowing you to edit the
- Message Parameters.
-
-
-
- 2.3.1.4 Edit
-
- Allows you to modify an existing message. It calls the configured
- Text Editor allowing you to edit the body of the current message.
- As soon as you close the editor it opens the Message Parameters
- Window allowing you to edit the Message Parameters.
-
-
-
- 2.3.1.5 Edit Hdr
-
- Allows you to modify the header of an existing message. It opens
- the Message Parameters Window allowing you to edit the parameters
- of the current message.
-
-
-
- 2.3.1.6 Reply
-
- Allows you to reply to the current message. It reformats and
- quotes the message, next it calls the configured Text Editor
- allowing you to insert your reply.
- As soon as you close the editor it opens the Message Parameters
- Window allowing you to edit the Message Parameters.
-
-
-
- 2.3.1.7 X Reply
-
- Performs the same operation as the Reply function, but it opens a
- requester allowing you to select the area where you want to post
- your reply.
-
-
-
-
-
- 2.3.2 Browse Window Menus
-
-
- 2.3.2.1 Messages
-
-
- 2.3.2.1.1 Delete
-
- Toggles the status of the Deleted Flag on the current message.
-
-
-
- 2.3.2.1.2 Protect
-
- Toggles the status of the Protected Flag on the current message.
-
-
-
- 2.3.2.1.3 Mark
-
- Toggles the status of the Marked Flag on the current message.
-
-
-
- 2.3.2.1.4 Archive
-
- Opens a file requester allowing you to select the file where you
- want to save the current message.
- You can configure the default name of the file with the
- 'Archive File' parameter.
-
-
-
- 2.3.2.1.5 Print
-
- Prints the current message on the configured printer.
-
-
-
- 2.3.2.1.6 Toggle UnReplied Flag
-
- Toggles the status of the UnReplied Flag on the current message.
-
-
-
-
- 2.3.2.2 Miscellaneous
-
-
- 2.3.2.2.1 File Request
-
- Opens the MM File Request window. The Node string gadget will
- be pre-filled with the originating address of the current
- message.
- You can enter the names of the files you want to request to the
- node in the string gadget below the listview.
- To delete a file just select it from the listview, clear the
- string gadget and press enter.
- If a requested file is already present in the .REQ file, it
- won't be added again.
-
-
-
- 2.3.2.2.2 Areas Window
-
- Goes Back to the Areas Window
-
-
-
- 2.3.2.2.3 Areas List
-
- Opens a requester allowing you to select the area where you want
- to go.
-
-
-
- 2.3.2.2.4 Previous Area
-
- Goes to the previous area.
-
-
-
- 2.3.2.2.5 Next Area
-
- Goes to the next area.
-
-
-
- 2.3.2.2.6 Previous UnRead Area
-
- Goes to the previous area with unread messages.
-
-
-
- 2.3.2.2.7 Next UnRead Area
-
- Goes to the next area with unread messages.
-
-
-
- 2.3.2.2.8 Export Area
-
- Performs an export of the current area.
-
-
-
-
- 2.3.2.3 Environment
-
-
- 2.3.2.3.1 Text Styles
-
- If this menu is selected, Mail Manager will show text surrounded
- by one of the following characters in a different style: `*'
- for bold text, `/' for italic text and `_' for underlined text.
- You can configure the initial state of this menu item with the
- 'Text Styles' parameter.
-
-
-
- 2.3.2.3.2 Show Kludges
-
- If this menu is selected, Mail Manager will show the kludges and
- the control lines of the message.
- You can configure the initial state of this menu item with the
- 'Show Kludges' parameter.
-
-
-
- 2.3.2.3.3 Quote Kludges
-
- If this menu is selected, Mail Manager will include kludges and
- control lines in the quoted message.
- You can configure the initial state of this menu item with the
- 'Quote Kludges' parameter.
-
-
-
-
- 2.3.2.4 User
-
- This menu lists all the user definable commands you have
- configured as Custom Browse Commands. When you select one of its
- items the associated command will be launched with the AmigaDOS
- 'Run' command.
-
-
-
-
-
- 2.3.3 Browse Window ShortCuts
-
- In the Browse Window you can use all the configured keyboard
- shortcuts for a MUI listview, besides those Mail Manager offers you
- a few extra hardcoded keyboard shortcuts for moving within messages.
-
-
- 2.3.3.1 Left
-
- Reads the previous message.
-
-
- 2.3.3.2 Right
-
- Reads the next message.
-
-
- 2.3.3.3 Shift+Left
-
- Reads the previous message in the reply thread without changing
- the parent message.
-
-
- 2.3.3.4 Shift+Right
-
- Reads the next message in the reply thread without changing the
- parent message.
-
-
- 2.3.3.5 Alt+Left
-
- Reads the previous message in the reply thread and makes it the
- the parent message.
-
-
- 2.3.3.6 Alt+Right
-
- Reads the next message in the reply thread and makes it the the
- parent message.
-
-
- 2.3.3.7 Control+Left
-
- Reads the previous unread message.
-
-
- 2.3.3.8 Control+Right
-
- Reads the next unread message.
-
-
- 2.3.3.9 Space
-
- Scrolls the message one page down. When you reach the end of the
- message it will read the next message.
- When you reach the end of the messages in the area it goes to the
- next area with unread messages, and starts reading the first
- unread message.
-
-
- 2.3.3.10 Shift+Space
-
- Scrolls the message one page up. When you reach the top of the
- message it will read the previous message.
- When you reach the top of the messages in the area it goes to the
- previous area with unread messages, and starts reading the first
- unread message.
-
-
- 2.3.3.11 Return
-
- Scrolls the message one page down. When you reach the end of the
- message it will read the next unread message.
- When you reach the end of the messages in the area it goes to the
- next area with unread messages, and starts reading the first
- unread message.
-
-
- 2.3.3.12 Del
-
- Toggles the status of the Deleted flag on the current message,
- it then reads the next message.
-
-
-
-
-
-
- 2.4 Message Parameters Window
-
- This window allows you to set or modify the parameters and the
- attributes of a message.
-
-
- 2.4.1 From
-
- Here you can insert the name of the sender of the message.
- If you click on the associated popup gadget or if you press
- RightAmiga+'?' while this string gadget is active, Mail Manager
- will open a window where you can select one of the configured Sysop
- names.
- In netmail areas, beside the From string gadget there is another
- string gadget where you can insert the address of the sender of the
- message. Normally you don't have to worry about the contents of
- this gadget, During the export operation Mail Manager will scan the
- configured Addresses ( Akas won't be scanned ) and will
- automatically choose the right one ( normally the nearer to the
- destination address ). If you instead want to force Mail Manager
- to use a particular address you can insert it in the string gadget
- and then select the 'Force Address' gadget. If you click on the
- associated popup gadget or if you press RightAmiga+'?' while this
- string gadget is active, Mail Manager will open a window where you
- can select one of the configured Addresses or Akas, and if you
- select one of these, Mail Manager will automatically select the
- 'Force Address' gadget.
-
-
- 2.4.2 To
-
- Here you can insert the name of the addressee of the message.
- If you insert here one of the nick names specified in the Userlist
- and press 'Return' Mail Manager will expand it to the associated
- name.
- If you instead insert here the name of one of the senders /
- addressees of the messages contained in the area and press
- 'Return', Mail Manager will fill the To Address field with the
- address of the user.
- If you click on the associated popup gadget or if you press
- RightAmiga+'?' while this string gadget is still active, Mail
- Manager will open a window where you can select one of the names
- inserted in the Userlist. If you have inserted a pattern in the
- string gadget ( you can use all the AmigaDOS wildcards ), Mail
- Manager will insert in the list only the names that match with that
- pattern.
- In netmail areas Mail Manager offers you also a powerful nodelist
- support ( you must have traplist.library and a compiled nodelist ).
- If you enter a pattern in the To string gadget and then press
- RightAmiga+'!' while this string gadget is still active, Mail
- Manager will ask you the number of the zone you want to limit the
- search to ( enter 0 for no limitation ), and then it will search in
- the Nodelist all the sysops that match that pattern. It could be
- a bit slow, particularly if you do not limit the search to a single
- zone, but I think that Mail Manager is the only one able to do
- this, and I find this really really useful.
- In netmail areas, besides the To string gadget there is another
- string gadget where you can insert the address of the addressee of
- the message. As soon as you press 'Return' Mail Manager will
- expand the address and, if the To string gadget is empty, it will
- scan the nodelist looking for the node and if it finds the
- corresponding entry it will fill the To string gadget with the name
- of the sysop of that node.
-
-
- 2.4.3 Subj
-
- Here you can insert the subject of the message.
-
-
- 2.4.4 Origin
-
- Here you can insert the text that will be inserted in the origin
- line of echomail messages.
- If you click on the associated popup gadget or if you press
- RightAmiga+'?' while this string gadget is still active, Mail
- Manager will open a window where you can select one of the
- configured Origin lines.
-
-
- 2.4.5 Flavor
-
- This radio gadget will set the flavor of a netmail message.
-
-
- 2.4.6 Private
-
- This checkmark gadget will set the status of the Private attribute
- of a message.
-
-
- 2.4.7 Reflow Text
-
- If this checkmark gadget is selected, Mail Manager will reflow the
- body of the message before writing it into the message base.
-
-
- 2.4.8 File Attached
-
- When you select this gadget Mail Manager will open an ASL file
- requester allowing you to select the file you want to attach to the
- message, then it will insert the filename in the subject of the
- message ( the path will be removed during the export operation ).
- Mail Manager is able to manage file attached also in Echo areas, all
- you have to do is to configure the area as 'File Echo'. Be careful,
- file attached in echo areas are supported by a few programs and
- normally it is not legal to send them into normal echo areas.
-
-
- 2.4.9 Force Address
-
- Normally during the export operation Mail Manager ignores the
- address inserted in the From Address string gadget, and
- automatically choose the better one within the configured addresses.
- If you instead want to force Mail Manager to use a particular
- address you can insert the address in the From Address string gadget
- and then select the 'Force Address' gadget.
-
-
- 2.4.10 Multi Send
-
- This gadget allows you to send a netmail message to many different
- persons. If you select this gadget, the Message Parameters Window
- won't be closed when you click on the 'Ok' gadget, allowing you to
- insert new parameters for another copy of the message. When you
- have finished you can close the window with the 'Cancel' gadget.
-
-
- 2.4.11 Receipt Request
-
- Sets the Return Receipt Request attribute to a netmail message.
-
-
-
-
-
-
-
- 3 MAIL MANAGER AREXX INTERFACE
-
- Mail Manager offers you a powerful Arexx interface.
-
- Some ARexx commands ( followed by a (***) in the description ), could
- create problems if the Editor isn't in the Areas Window. MM solves this
- problem going automatically back to the Areas Window as soon as one of
- this commands is executed.
-
- Of course this is not a good solution if this happens while you, for
- example, are reading or writing a message. You can solve this 'problem'
- by checking the result of the Command 'MM_AreasWin' before executing one
- of this commands. If RC = 5 you can wait a few seconds with delay() (
- remember to load the rexxsupport.library ) and check again. As soon as
- RC = 0 you can safely launch the command.
-
- Example:
-
- /*
- ** This script shows a nice and safe way for calling the Import function
- */
-
- address 'MAILMANAGER'
-
- MM_AreasWin
- if RC ~= 0 then do
- text = 'Please go back to the Areas Window as soon as possible'
- gadget = "*_Ok"
- MM_Requester '"There is an ARexx script waiting..."' 'text' 'gadget'
- end
-
- do until RC = 0
- call Delay(250)
- MM_AreasWin
- end
-
- MM_Import
-
- exit
-
-
-
-
- 3.1 Standard MUI ARexx commands
-
-
- 3.1.1 Quit
-
- Syntax: Quit
- Function: Shuts Down Mail Manager.
-
-
-
- 3.1.2 Hide
-
- Syntax: Hide
- Function: Iconifies Mail Manager.
-
-
-
- 3.1.3 Show
-
- Syntax: Show
- Function: UnIconifies Mail Manager.
-
-
-
- 3.1.4 Help
-
- Syntax: Help FILE/A
- Function: Writes a list of all the ARexx commands of Mail Manager
- to the specified file.
-
-
-
-
-
-
- 3.2 Mail Manager internal ARexx commands
-
-
- 3.2.1 Ticks Management
-
-
- 3.2.1.1 MM_ImportTicks
-
- Syntax: MM_ImportTicks
-
- Function: Launches MM Ticks Import function
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.1.2 MM_HatchTick
-
- Syntax: MM_HatchTick AREATAG/A, STEM/A
-
- Function: Inserts a Tick File in the area specified in <AREATAG>.
-
- Input: <STEM>.FILE - Name of the File you want to send.
- <STEM>.DESC - File Description
- <STEM>.REPL - File to replace
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2 Areas Management
-
-
- 3.2.2.1 MM_Import (***)
-
- Syntax: MM_Import
-
- Function: Launches MM Import function
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.2.2 MM_Export
-
- Syntax: MM_Export AREATAG/F
-
- Function: If you specify an <AREATAG> it Exports that Area,
- otherwise it Exports All the Areas.
- If <AREATAG> = SMARTEXPORT it exports all the areas
- flagged with 'E'. Be careful, MM knows that an external
- program has written a message into an area only after a
- Scan of the area. So if an external prg has written a
- message into an area and you have not scanned that
- area, "MM_Export 'SMARTEXPORT'" won't export that
- message. In general 'SMARTEXPORT' is useful only with
- messages written or imported from Mail Manager. If you
- want to be sure to export also messages written from
- external programs you must perform a global Export.
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.3 MM_Rescan
-
- Syntax: MM_Rescan AREATAG/A, NODE/A, FORCED/S
-
- Function: Performs a Rescan of the Area <AREATAG> for Node <NODE>.
- If you specify the switch 'FORCED', MM will Export to
- the Node also messages already exported to the node.
-
- Result: RC = 0 - All OK
- RC = 1 - Reserved
- RC = 2 - Reserved
- RC = 3 - Unknown Node
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.4 MM_Scan
-
- Syntax: MM_Scan AREATAG/F
-
- Function: If you specify an <AREATAG> it Scans that Area,
- otherwise it Scans All the Areas
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.5 MM_Free (***)
-
- Syntax: MM_Free AREATAG/F
-
- Function: If you specify an <AREATAG> it Frees the Memory
- associated to that Area and writes the Index.
- Otherwise it Frees All the Areas
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.6 MM_Update
-
- Syntax: MM_Update AREATAG/F
-
- Function: If you specify an <AREATAG> it writes the Index
- associated to that Area. Otherwise it writes All the
- Indexes. In any case it won't free the associated
- Memory.
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.7 MM_WriteStats
-
- Syntax: MM_WriteStats
-
- Function: Writes the Statistics File
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.2.8 MM_Renumber
-
- Syntax: MM_Renumber AREATAG/F
-
- Function: If you specify an <AREATAG> it Renumbers that Area,
- Otherwise it Renumbers all the Areas. This function is
- active only only with Areas in PLAIN or IDX MsgBases.
- Be careful !!! This function does not update the link
- fields of the message header ( used for example from
- DLG ), so DLG users should renumber their MsgBases only
- with the DLG internal Renumber function.
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.9 MM_Optimize
-
- Syntax: MM_Optimize AREATAG/F
-
- Function: If you specify an <AREATAG> it Optimizes the text file
- of that Area, Otherwise it Optimizes all the Areas.
- This function is active only with Areas in Quick or
- Compressed MsgBases
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.10 MM_Delete (***)
-
- Syntax: MM_Delete AREATAG/F
-
- Function: If you specify an <AREATAG> it Deletes Messages from
- that Area. Otherwise it Deletes Messages from all the
- Areas.
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.11 MM_Purge (***)
-
- Syntax: MM_Purge AREATAG/F
-
- Function: If you specify an <AREATAG> it Deletes Messages from
- that Area. Otherwise it Deletes Messages from all the
- Areas. In any case UnRead Messages won't be deleted
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.2.12 MM_CleanArea (***)
-
- Syntax: MM_CleanArea AREATAG/A
-
- Function: It scans the area specified in <AREATAG> deleting all
- the Messages flagged as 'DEL'
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
-
-
-
-
- 3.2.3 Messages Management
-
-
- 3.2.3.1 MM_EditMsgFlags
-
- Syntax: MM_EditMsgFlags AREATAG/A, MSGNUM/A, VARNAME/A
-
- Function: Edits the Flags of the Message number <MSGNUM> in the
- Area <AREATAG> using data stored in the variable
- <VARNAME>.
- Possible values for the flags stored in <VARNAME>:
-
- Sets the Flag Clears the Flag
- ------------- ---------------
- UNR !UNR
- SYS !SYS
- READ !READ
- SENT !SENT
- MARK !MARK
- SAFE !SAFE
- DEL !DEL
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area or Unknown Msg
-
-
-
- 3.2.3.2 MM_SearchMsgs
-
- Syntax: MM_SearchMsgs AREATAG/A,STEM/A,FROM/A,TO/A,SUBJ/A,FLAGS/M
-
- Function: Fills the Stem <STEM> with the Number of the Messages of
- the Area <AREATAG> that match the Patterns ( AmigaDOS
- wildcards allowed ) specified in <FROM>, <TO>, <SUBJ>
- with the Attributes <FLAGS>.
-
- Possible values for <FLAGS>:
-
- SENT - MSG has been already Exported
- INTR - MSG isn't addressed to one of the Addresses
- or Akas configured.
- READ - MSG has been Read
- UNR - MSG is UnReplied
- IMP - MSG has been Imported
- !SENT - MSG Must be Exported
- !INTR - MSG is addressed to one of the Addresses
- or Akas configured.
- !READ - MSG hasn't been Read
- !UNR - MSG in Replied
- !IMP - MSG hasn't been Imported (was written on the
- system)
-
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
- <STEM>.COUNT - Number of Messages in the Stem
- <STEM>.<n> - Number of the Msg ( <n> = 0 to COUNT-1 )
-
-
-
- 3.2.3.3 MM_ReadMsg
-
- Syntax: MM_ReadMsg AREATAG/A, MSGNUM/A, STEM/A
-
- Function: Reads the Message number <MSGNUM> in the Area <AREATAG>
- and fills the Stem <STEM>
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area or Unknown Message
- <STEM>.FROM - Name of the Sender of the Msg
- <STEM>.FROMADDR - Address of the Sender of the Msg
- <STEM>.TO - Name of the Addressee of the Msg
- <STEM>.TOADDR - Address of the Addressee of the Msg
- <STEM>.SUBJ - Subject of the Msg
- <STEM>.DATE - Creation Date of the Msg
- <STEM>.FLAGS - Flags of the Msg
- PVT CRASH HOLD SENT INTR KILL RRR FATT
- UNR SYS READ IMP MARK SAFE DEL
- <STEM>.HEAD.COUNT - Number of Kludge Lines in the Msg
- <STEM>.HEAD.<n> - Kludge Line Number <n>
- ( <n> = 0 to COUNT-1 )
- <STEM>.TEXT.COUNT - Number of Text Lines in the Msg
- <STEM>.TEXT.<n> - Text Line Number <n>
- ( <n> = 0 to COUNT-1 )
- <STEM>.FOOT.COUNT - Number of Control Lines in the Msg
- (Tear,Origin,Seen-By,Path,Via Node)
- <STEM>.FOOT.<n> - Control Line Number <n>
- ( <n> = 0 to COUNT-1 )
-
-
-
- 3.2.3.4 MM_WriteMsg
-
- Syntax: MM_WriteMsg AREATAG/A, STEM/A
-
- Function: Writes a message in the Area <AREATAG> reading data
- from Stem <STEM>
-
- Input: <STEM>.FROM - Name of the Sender of the Msg.
- Default: name specified as Default
- Sysop.
-
- <STEM>.FROMADDR - Address of the Sender of the Msg
- The address passed here WON'T be
- changed during Export. If you want
- to use your Address nearer to the
- destination of the MSG you must pass
- an empty string ("") here.
-
- <STEM>.TO - Name of the Addressee of the Msg
- Default: ""
-
- <STEM>.TOADDR - Address of the Addressee of the Msg.
- If the area is a NetMail area you
- MUST supply a valid address
-
- <STEM>.SUBJ - Subject of the Msg. Default: ""
-
- <STEM>.TEAR - The contents of this variable will
- be added to the end of the standard
- MM tear line. Max 16 Chrs.
- Default: ""
-
- <STEM>.ORIGIN - Origin line Default: The origin
- configured for the area.
-
- <STEM>.FLAGS - Flags of the Msg: REFLOW, PVT, CRASH,
- SENT, FATT, KILL, HOLD, RRR,
- Default: "PVT" in NetMail areas
-
- <STEM>.FILE - Name of the file containing the Text
- of the MSG. Default: "T:MM.TRANS"
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
-
-
-
- 3.2.3.5 MM_EditMsg
-
- Syntax: MM_EditMsg AREATAG/A, MSGNUM/A, STEM/A
-
- Function: Edits the Message number <MSGNUM> in the Area <AREATAG>
- using data stored in the Stem <STEM>.
- Undefined fields or empty fields leave unchanged that
- part of the header.
-
- Input: <STEM>.FROM - Name of the Sender of the Msg
-
- <STEM>.FROMADDR - Address of the Sender of the Msg
-
- <STEM>.TO - Name of the Addressee of the Msg
-
- <STEM>.TOADDR - Address of the Addressee of the Msg
-
- <STEM>.SUBJ - Subject of the Msg
-
- <STEM>.FLAGS - Flags of the Msg
- Set the Flag Clear the Flag
- ------------ --------------
- PVT !PVT
- CRASH !CRASH
- SENT !SENT
- FATT !FATT
- KILL !KILL
- HOLD !HOLD
- RRR !RRR
-
- <STEM>.FILE - Name of the file containing the Text
- of the MSG. If not specified, the
- text will be left unchanged.
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area or Unknown Msg
-
-
-
- 3.2.3.6 MM_DeleteMsg (***)
-
- Syntax: MM_DeleteMsg AREATAG/A, MSGNUM/A
-
- Function: Deletes the Msg number <MSGNUM> in the Area <AREATAG>
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area or Unknown Msg
-
-
-
-
-
-
-
- 3.2.4 Configuration Management
-
-
- 3.2.4.1 MM_LoadCfg (***)
-
- Syntax: MM_LoadCfg FILE/F
-
- Function: Loads the configuration. If <FILE> is not specified,
- it will reload the actual configuration file.
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.4.2 MM_SaveCfg
-
- Syntax: MM_SaveCfg FILE/F
-
- Function: Saves the Configuration. If <FILE> is not specified,
- it will save the configuration with the same name of
- the last loaded configuration File.
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.4.3 MM_GetSysop
-
- Syntax: MM_GetSysop VARNAME/A
-
- Function: Fills the variable <VARNAME> with the Name of the SysOp
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.4.4 MM_GetAddrs
-
- Syntax: MM_GetAddrs STEM/A
-
- Function: Fills the Stem <STEM> with your Addresses and Akas
-
- Result: RC = 0 - All OK
- <STEM>.COUNT - Number of configured Nodes
- <STEM>.<n> - Address of you Address <n>
- <n> = 0 to COUNT-1
-
-
-
- 3.2.4.5 MM_GetNearestAddr
-
- Syntax: MM_GetNearestAddr NODE/A, VARNAME/A
-
- Function: Fills the variable <VARNAME> with your Address nearest
- to the Node <NODE>. It doesn't considers your Akas.
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.4.6 MM_GetGroups
-
- Syntax: MM_GetGroups STEM/A
-
- Function: Fills the Stem <STEM> with the name of the Groups
- configured
-
- Result: RC = 0 - All OK
- <STEM>.COUNT - Number of configured Groups
- <STEM>.<n> - Name of the Group <n>
- <n> = 0 to COUNT-1
-
-
-
- 3.2.4.7 MM_GetGroupAreas
-
- Syntax: MM_GetGroupAreas STEM/A, GROUP/A, LEVEL/A
-
- Function: Fills the Stem <STEM> with the Names of the Areas
- belonging to the group <GROUP>, and the access levels
- required for the areas within the group.
- If <LEVEL> != 0 MM will return only areas with an
- access level <= <LEVEL>
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Group
- <STEM>.COUNT - Number of Areas belonging to the
- group
- <STEM>.<n>.AREA - Tag Name of the Area <n>
- <n> = 0 to COUNT-1
- <STEM>.<n>.LEVEL - access level required for this area
- within the group.
-
-
-
- 3.2.4.8 MM_GetGroupTickAreas
-
- Syntax: MM_GetGroupTickAreas STEM/A, GROUP/A, LEVEL/A
-
- Function: Fills the Stem <STEM> with the Names of the Tick Areas
- belonging to the group <GROUP>, and the access levels
- required for the areas within the group.
- If <LEVEL> != 0, MM will return only areas with an
- access level <= <LEVEL>
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Group
- <STEM>.COUNT - Number of Areas belonging to the group
- <STEM>.<n>.AREA - Name of the Area number <n>
- <n> = 0 to COUNT-1
- <STEM>.<n>.LEVEL - access level required for area <n>
- within the group.
-
-
-
- 3.2.4.9 MM_GetNodes
-
- Syntax: MM_GetNodes STEM/A
-
- Function: Fills the Stem <STEM> with the Addresses of the Nodes
- configured
-
- Result: RC = 0 - All OK
- <STEM>.COUNT - Number of configured Nodes
- <STEM>.<n> - Address of the Node <n>
- <n> = 0 to COUNT-1
-
-
-
- 3.2.4.10 MM_GetNodeInfo
-
- Syntax: MM_GetNodeInfo NODE/A, STEM/A
-
- Function: Fills the Stem <STEM> with some information about the
- Node <NODE>
-
- Result: RC = 0 - All OK
- RC = 3 - Unknown Node
- <STEM>.ADDRDIM - Dim. of the Seen-By/Path lines
- in messages exported to the
- Node: 2, 4, 5.
- <STEM>.PACKDIM - Dim. of the PKTs created for
- the Node: 3, 4, 5.
- <STEM>.ECHOFLAVOR - Flavor of Echomail PKTs created
- for the Node: NORMAL, DIRECT,
- HOLD, CRASH, VIRTUAL.
- <STEM>.TICKFLAVOR - Flavor of Tick Files created
- for the Node: NORMAL, DIRECT,
- HOLD, CRASH, VIRTUAL.
- <STEM>.PKTPW - Packet Password for the Node
- <STEM>.AREAFIXPW - AreaFix Password for the Node
- <STEM>.TICKPW - Tick Password for the Node
- <STEM>.USERFLAGS - User Flags for the Node
- <STEM>.GROUPCOUNT - Number of groups the node
- belongs to.
- <STEM>.GROUPNAME.<n> - Name of the group number <n>
- <n> = 0 to GROUPCOUNT-1
- <STEM>.GROUPLEVEL.<n> - Access level of the Node within
- the group number <n>
- <STEM>.AREA.COUNT - Number of Areas the node is
- connected to.
- <STEM>.AREA.<n> - Tag Name of the area number <n>
- <n> = 0 to AREA.COUNT - 1
- <STEM>.TICKAREA.COUNT - Number of the Tick Areas the
- node is connected to.
- <STEM>.TICKAREA.<n> - Tag Name of the Tick Area
- number <n>.
- <n> = 0 to TICKAREA.COUNT - 1
-
-
-
- 3.2.4.11 MM_GetCfgPaths
-
- Syntax: MM_GetCfgPaths STEM/A
-
- Function: Fills the Stem <STEM> with some paths configured.
-
- Result: RC = 0 - All OK
- <STEM>.EDITOR - Editor command
- <STEM>.INBOUND - Inbound dir
- <STEM>.OUTBOUND - Outbound dir
- <STEM>.BUNDLEDIR - Outgoing Bundles dir
- <STEM>.TICDIR - Outgoing *.TIC dir
- <STEM>.TEMPPKTDIR - Temporary Outgoing Pkts dir
- <STEM>.BADDIR - Bad dir
- <STEM>.BACKUPDIR - Backup dir
- <STEM>.WORKDIR - Working dir
- <STEM>.MAILDEV - Mail device
- <STEM>.USERLIST - UserList file
- <STEM>.NODELISTDIR - Nodelist dir
-
-
-
-
-
- 3.2.4.12 MM_GetAreas
-
- Syntax: MM_GetAreas STEM/A, AREATYPES/M
-
- Function: Fills the Stem <STEM> with the Tag Names of the Areas
- configured. If you specify some AREATYPES, MM will
- consider only areas with those AreaTypes. Possible
- values for <AREATYPES>:
- MAIL - Areas of type MAIL
- FECHO - Areas of type FECHO
- ECHO - Areas of type ECHO and FECHO
- BAD - Areas of type BAD
-
- Result: RC = 0 - All OK
- <STEM>.COUNT - Number of configured Areas
- <STEM>.<n> - Tag Name of the Area <n>
- <n> = 0 to COUNT-1
-
-
-
- 3.2.4.13 MM_GetAreaInfo
-
- Syntax: MM_GetAreaInfo AREATAG/A, STEM/A
-
- Function: Fills the Stem <STEM> with some information about the
- Area <AREATAG>
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
- <STEM>.NAME - Name of the area
- <STEM>.DESC - Description of the area
- <STEM>.PATH - Path of the area
- <STEM>.ALTPATH - Alternate Path of the area
- <STEM>.GROUP - Name of the group this area belongs
- to
- <STEM>.LEVEL - Access level required for this area
- within the group
- <STEM>.ADDR - Your Address in this area
- <STEM>.NODE.COUNT - Number of Nodes linked to the area
- <STEM>.NODE.<n> - Addresses of node number <n>
- <n> = 0 to COUNT-1
- <STEM>.TYPE - Type of the area: MAIL, ECHO, FECHO,
- BAD
- <STEM>.MBASE - Message Base used for the area:
- PLAIN, IDX, QUICK, COMP, PTHRO
- <STEM>.NMSG - Number of the Messages in the area
- <STEM>.HIMSG - Number of the last Message in the
- area
-
-
-
- 3.2.4.14 MM_CreateArea
-
- Syntax: MM_CreateArea AREATAG/A, PATH/A, ADDR/A, MSGBASE/A,
- GROUP/A, GROUPLEVEL/A, NODE/A
-
- Function: Creates a New Echo Area adding it to the configuration,
- then saves it. It also connects the Node <NODE> to the
- Area. The area is created with the following defaults:
-
- Tag = <AREATAG>
- Name = Tag
- Path = <PATH>Tag/
- Address = <ADDR>
- MsgBase = <MSGBASE> - PLAIN, IDX, QUICK, COMP, PTHRO
- Show = All
- OrderBy = Number
- DeleteBy = Number
- NDelete = 200
- GroupName = <GROUP>
- GroupLevel = <GROUPLEVEL>
-
-
- Result: RC = 0 - All OK
- RC = 1 - Area Already defined
- RC = 2 - Unknown Address
- RC = 3 - Unknown Node
- RC = 4 - Unknown Group
-
-
-
- 3.2.4.15 MM_AddAreaNode
-
- Syntax: MM_AddAreaNode AREATAG/A, NODE/A, ACCESS/F
-
- Function: Connects the Node <NODE> to Area <AREATAG>.
- If you specify READONLY as <ACCESS>, messages coming
- from that node won't be imported in the area.
- If you instead specify WRITEONLY as <ACCESS> messages
- won't be exported to that node,
-
-
- Result: RC = 0 - All OK
- RC = 1 - The Node is already Connected to the Area
- RC = 2 - Reserved
- RC = 3 - Unknown Node
- RC = 4 - Unknown Area
-
-
-
- 3.2.4.16 MM_DelAreaNode
-
- Syntax: MM_DelAreaNode AREATAG/A, NODE/A
-
- Function: Disconnect the Node <NODE> from Area <AREATAG>
-
- Result: RC = 0 - All OK
- RC = 1 - Node is not connected to the Area
- RC = 2 - Reserved
- RC = 3 - Unknown Node
- RC = 4 - Unknown Area
-
-
-
- 3.2.4.17 MM_GetTickAreas
-
- Syntax: MM_GetTickAreas STEM/A
-
- Function: Fills the Stem <STEM> with the Tag Names of the Tick
- Areas configured.
-
- Result: RC = 0 - All OK
- <STEM>.COUNT - Number of configured Areas
- <STEM>.<n> - Tag Name of the Area number <n>
- <n> = 0 to COUNT-1
-
-
-
- 3.2.4.18 MM_GetTickAreaInfo
-
- Syntax: MM_GetTickAreaInfo AREATAG/A, STEM/A
-
- Function: Fills the Stem <STEM> with some information about the
- Tick Area <AREATAG>
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Area
- <STEM>.DESC - Description of the area
- <STEM>.PATH - Path of the area
- <STEM>.ALTPATH - Alternate Path of the area
- <STEM>.GROUP - Name of the group this area belongs
- to
- <STEM>.LEVEL - Access level required for this area
- within the group
- <STEM>.ADDR - Your Address in this area
- <STEM>.NODE.COUNT - Number of Nodes linked to the area
- <STEM>.NODE.<n> - Address of nodes number <n>
- <n> = 0 to COUNT-1
-
-
-
- 3.2.4.19 MM_AddTickAreaNode
-
- Syntax: MM_AddTickAreaNode AREATAG/A, NODE/A, ACCESS/F
-
- Function: Connects the Node <NODE> to the Tick Area <AREATAG>
- If you specify READONLY as <ACCESS>, Tick files coming
- from that node won't be imported in the area.
- If you instead specify WRITEONLY as <ACCESS> Tick files
- won't be exported to that node,
-
- Result: RC = 0 - All OK
- RC = 1 - The Node is already Connected to the Area
- RC = 2 - Reserved
- RC = 3 - Unknown Node
- RC = 4 - Unknown Area
-
-
-
-
- 3.2.4.20 MM_DelTickAreaNode
-
- Syntax: MM_DelTickAreaNode AREATAG/A, NODE/A
-
- Function: Disconnect the Node <NODE> from Area <AREATAG>
-
- Result: RC = 0 - All OK
- RC = 1 - The Node is not connected to the Area
- RC = 2 - Reserved
- RC = 3 - Unknown Node
- RC = 4 - Unknown Area
-
-
-
-
-
-
-
- 3.2.5 Miscellaneous Management
-
-
- 3.2.5.1 MM_GetNodelistNode
-
- Syntax: MM_GetNodelistNode NODE/A, STEM/A
-
- Function: Finds the node <NODE> in the nodelist and fills the
- Stem <STEM> with some information about the node.
-
- Result: RC = 0 - All OK
- RC = 4 - Unknown Node
- RC = 5 - Unable to open the Nodelist
- <STEM>.SYSTEM - Name of the System
- <STEM>.SYSOP - Name of the Sysop
- <STEM>.CITY - City and State
- <STEM>.PHONE - Phone Number
- <STEM>.BAUDRATE - Baud Rate
- <STEM>.FLAGS - Nodelist Flags
-
-
-
- 3.2.5.2 MM_RequestFiles
-
- Syntax: MM_RequestFiles NODE/A, STEM/A
-
- Function: Opens the MM FileRequest window, and fills it with the
- node <NODE> and the files listed in the Stem <STEM>.
-
- Input: <STEM>.COUNT - Number of files to be requested
- <STEM>.<n> - File number <n>. <n> = 0 to COUNT-1
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.5.3 MM_AddToFlow
-
- Syntax: MM_AddToFlow FILE/A, NODE/A, TYPE/A
-
- Function: Adds the file <FILE> to a Flow file of type <TYPE> for
- the Node <NODE>. If the File is already present in the
- Flow File, it will NOT be added again.
-
- Input: <TYPE> - Type of the Flow File:
- REQ, NORMAL, DIRECT, CRASH, HOLD
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.5.4 MM_AreasWin
-
- Syntax: MM_AreasWin
-
- Function: Check if the Areas Window is opened
-
- Result: RC = 0 - Areas Window is opened or MM is iconified
- RC = 5 - Areas Window is not opened
-
-
-
- 3.2.5.5 MM_WriteLog
-
- Syntax: MM_WriteLog VARNAME/A, LEVEL/A
-
- Function: Writes the string contained in <VARNAME> to the logs
- with a LogLevel higher than <LEVEL>
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.5.6 MM_CloseLog
-
- Syntax: MM_CloseLog
-
- Function: Closes the Log file
-
- Result: RC = 0 - All OK
-
-
-
-
-
-
-
- 3.2.6 Requesters Management
-
- 3.2.6.1 MM_Requester
-
- Syntax: MM_Requester TITLE/A, TEXTVAR/A, GADGETSVAR/A
-
- Function: Opens a MUI requester containing the text stored in
- <TEXTVAR> and allowing the user to select on one of the
- gatdgets specified in <GADGETSVAR>
-
- Input: <TITLE> - Title of the Requester
- <TEXTVAR> - Name of the variable containing the Text
- of the Requester
- <GADGETSVAR> - Name of the variable containing the
- possible answers to the requester. The
- format looks like '*_Save|_Use|_Cancel'
- A '_' character indicates the keyboard
- shortcut for this gadget.
- A '*' character indicates the default
- gadget for the requester
-
- Result: RC = <n> - <n> = Number of the selected gadget
- from left to right = 1, 2, ..., 0.
-
-
-
- 3.2.6.2 MM_StringReq
-
- Syntax: MM_StringReq TITLE/A, VARNAME/A
-
- Function: Opens a MUI requester allowing the user to enter a
- string.
-
- Input: <TITLE> - Title of the Requester
- <VARNAME> - The default value of the requester will be
- read from <VARNAME>, and the same variable
- will be filled with the string inserted by
- the user
-
- Result: RC = 0 - The user pressed the OK gadget
- RC = 1 - The user pressed the Cancel gadget
- RC = 2 - The requester cannot be opened (MM iconified)
-
-
-
- 3.2.6.3 MM_FileReq
-
- Syntax: MM_FileReq VARNAME/A
-
- Function: Opens a File Requester allowing the user to select a
- File
-
- Input : <VARNAME> - The default value of the requester will be
- read from <VARNAME>, and the same variable
- will be filled with the File Selected by
- the user
-
- Result: RC = 0 - The user pressed the OK gadget
- RC = 1 - The user pressed the Cancel gadget
- RC = 2 - The requester cannot be opened (MM iconified)
-
-
-
- 3.2.6.4 MM_AreaReq
-
- Syntax: MM_AreaReq VARNAME/A
-
- Function: Opens a MUI Requester allowing the user to select an
- Area
-
- Input: <VARNAME> - Name of the variable that will be filled with
- the Tag Name of the Area Selected by the user
-
- Result: RC = 0 - The user pressed the OK gadget
- RC = 1 - The user pressed the Cancel gadget
- RC = 2 - The requester cannot be opened (MM iconified)
-
-
-
- 3.2.6.5 MM_SingleSelReq
-
- Syntax: MM_SingleSelReq INSTEM/A,OUTSTEM/A,TITLE/A,OUTSTEMTYPE/A
-
- Function: Opens a MUI requester with a SingleSelect ListView
- filled with the entries listed in <INSTEM>.
- <INSTEM>.COUNT should be filled with the number of
- entries. If <OUTSTEM>.COUNT = 1 <OUTSTEM>.0 will
- contain the entry selected from the user.
-
- Input: <INSTEM>.COUNT - Number of entries to be inserted in the
- listView
- <INSTEM>.<n> - Entry number <n>. <n> = 0 to COUNT-1
- <TITLE> - Title of the Requester
- <OUTSTEMTYPE> - Specifies the Type of value returned
- in <OUTSTEM>: NUM, STR
- NUM - number of the selected entry
- STR - value of the selected entry
-
-
- Result: RC = 0 - The user pressed the OK gadget
- RC = 1 - The user pressed the Cancel gadget
- RC = 2 - The requester cannot be opened (MM iconified)
-
- <OUTSTEM>.COUNT - 0 = No entry selected
- 1 = One Entry Selected
- <OUTSTEM>.0 - Selected Entry
-
-
-
- 3.2.6.6 MM_MultiSelReq
-
- Syntax: MM_MultiSelReq INSTEM/A,OUTSTEM/A,TITLE/A,OUTSTEMTYPE/A
-
- Function: Opens a MUI requester with a MultiSelect ListView
- filled with the entries listed in <INSTEM>.
- <INSTEM>.COUNT should be filled with the number of
- entries. It fills the Stem <OUTSTEM> with the entries
- selected from the user. The number of selected entries
- will be stored in <OUTSTEM>.COUNT
-
- Input: <INSTEM>.COUNT - Number of entries to be inserted in
- the listView
- <INSTEM>.<n> - Entry number <n>. <n> = 0 to COUNT-1
- <TITLE> - Title of the Requester
- <OUTSTEMTYPE> - Specifies the Type of value returned
- in <OUTSTEM>: NUM, STR
- NUM - number of the selected entry
- STR - value of the selected entry
-
- Result: RC = 0 - The user pressed the OK gadget
- RC = 1 - The user pressed the Cancel gadget
- RC = 2 - The requester cannot be opened (MM iconified)
-
- <OUTSTEM>.COUNT - Number of entries selected
- 0 = No entry selected
- <OUTSTEM>.<n> - Selected Entry number <n>
- <n> = 0 to COUNT-1
-
-
-
-
-
-
-
- 3.2.7 Stems Management
-
-
- 3.2.7.1 MM_WriteStem
-
- Syntax: MM_WriteStem FILE/A, STEM/A, APPEND/S
-
- Function: Writes to the file <FILE> the lines contained in the
- Stem <STEM> adding a LF to the end of every line.
- If you specify the switch 'APPEND', MM will append the
- lines to an existing file.
-
- Input: <FILE> - Output file
- <STEM>.COUNT - Number of lines in <STEM>
- <STEM>.<n> - Line number <n> <n> = 0 to COUNT-1
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.7.2 MM_ReadStem
-
- Syntax: MM_ReadStem FILE/A, STEM/A, APPEND/S
-
- Function: Fills the Stem <STEM> with the lines contained in the
- text file <FILE>. Every line must end with a LF.
- If you specify the switch 'APPEND', MM will append the
- lines to the end of the Stem ( <STEM>.COUNT should
- contain the number of lines already in the Stem ).
-
- Input: <FILE> - Input file
- <STEM>.COUNT - Number of lines already in <STEM>.
- <STEM>.<n> - Line number <n> <n> = 0 to COUNT-1
-
- Result: RC = 0 - All OK
- <STEM>.COUNT - Number of lines in <STEM>.
- <STEM>.<n> - Line number <n> <n> = 0 to COUNT-1
-
-
-
- 3.2.7.3 MM_SearchInStem
-
- Syntax: MM_SearchInStem INSTEM/A,OUTSTEM/A,PATTERN/A,OUTSTEMTYPE/A
-
- Function: Fills the Stem <OUTSTEM> with the entries in the Stem
- <INSTEM> that match with the pattern <PATTERN>. The
- search is CASE INSENSITIVE.
-
- Input: <INSTEM>.COUNT - Number of entries in <INSTEM>
- <INSTEM>.<n> - Entry number <n> <n> = 0 to COUNT-1
- <PATTERN> - Matching pattern
- All AmigaDOS WildCards are allowed
- <OUTSTEMTYPE> - Specifies the Type of value returned
- in <OUTSTEM>: NUM, STR
- NUM - number of the selected entry
- STR - value of the selected entry
-
- Result: RC = 0 - All OK
- <OUTSTEM>.COUNT - Number of entries in <OUTSTEM>
- <OUTSTEM>.<n> - Entry number <n> <n> = 0 to COUNT-1
-
-
-
- 3.2.7.4 MM_AddToStem
-
- Syntax: MM_AddToStem STEM/A, VARNAME/A
-
- Function: Adds the contents of the variable <VARNAME> to the end
- of the Stem <STEM>
-
- Input: <STEM>.COUNT - Number of entries in <STEM>
- <STEM>.<n> - Entry number <n> <n> = 0 to COUNT-1
- <VARNAME> - the contents of this variable will be
- added to the end of the Stem
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.7.5 MM_SortStem
-
- Syntax: MM_SortStem STEM/A
-
- Function: Sorts the Stem <STEM> in alphabetical order.
- The sorting is CASE SENSITIVE
-
- Input: <STEM>.COUNT - Number of entries in <STEM>
- <STEM>.<n> - Entry number <n> <n> = 0 to COUNT-1
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.7.6 MM_SortAddresses
-
- Syntax: MM_SortAddresses STEM/A
-
- Function: Sorts the Addresses contained in the Stem <STEM>
-
- Input: <STEM>.COUNT - Number of entries in <STEM>
- <STEM>.<n> - Entry number <n> <n> = 0 to COUNT-1
-
- Result: RC = 0 - All OK
-
-
-
-
-
-
-
- 3.2.8 Files Management
-
-
- 3.2.8.1 MM_CRCFile
-
- Syntax: MM_CRCFile FILE/A, VARNAME/A
-
- Function: Fills the variable <VARNAME> with the CRC-32 of the
- file <FILE>.
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.8.2 MM_CopyFile
-
- Syntax: MM_CopyFile FROM/A, TO/A
-
- Function: Copies the file <FROM> to the file <TO>. If <TO>
- already exists, MM will append a ",n" with n = 1 to 999
- to the destination filename.
- The FileNote will be preserved
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.8.3 MM_MoveFile
-
- Syntax: MM_MoveFile FROM/A, TO/A
-
- Function: Moves the file <FROM> to the file <TO>. If <TO>
- already exists, MM will append a ",n" with n = 1 to 999
- to the destination filename.
- The FileNote will be preserved
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.8.4 MM_DeleteFile
-
- Syntax: MM_DeleteFile FILE/A
-
- Function: Deletes the file <FILE>
-
- Result: RC = 0 - All OK
-
-
-
- 3.2.8.5 MM_SetFileNote
-
- Syntax: MM_SetFileNote FILE/A, VARNAME/A
-
- Function: Fills the FileNote of the file <FILE> with the contents
- of the variable <VARNAME>. The note may be up to 80
- characters long
-
- Result: RC = 0 - All OK
-
-
-
-
-
-
- 4 MISCELLANEOUS
-
- 4.1 Support
-
- If you have any suggestions, questions or BUG reports, you can reach
- me or my support-team at this addresses:
-
- Pino Aliberti German Support
- 2:335/602.2@fidonet Siggi Weisner
- 39:102/10.0@amiganet 2:2448/7022.0@fidonet
- aliberti@maui.nervous.com 39:170/505.29@amiganet
-
- There is also an international Amiganet Echomail conference called
- MM_AMY, which should be available at major backbones. This Area
- will allow the users and the author of Mail Manager to get closer
- together and keep a closer contact.
- In this area, you can freely exchange your experience with Mail
- Manager and discuss future enhancements you would like to see etc.
- The availability of new versions of Mail Manager will be announced
- there, too!
-
-
-
- 4.2 Registration
-
- Mail Manager is offered to you under the concepts of ShareWare.
- You can use it for an evaluation period of up to 4 weeks without
- paying any charge. If you are going to use Mail Manager after the
- evaluation period, you MUST register.
-
- The unregistered version of Mail Manager has some limitations:
- - The ARexx interface is disabled
- - The Optimize function is disabled
- - There are some registration requesters.
-
- Actually it is possible to register your copy of Mail Manager at one
- of these sites:
-
- Italy - Pino Aliberti 2:335/602.2@fidonet
- Germany - Siggi Weisner 2:2448/7022.0@fidonet
-
- The method for registering at each of these sites is a little
- different, so please read the instructions for each very carefully.
-
- **********************************************************************
- * *
- * NO PERSON(S) OR BUSINESSES OTHER THAN ME AND THE LISTED *
- * SUPPORTERS ARE AUTHORIZED TO ACCEPT ANY REGISTRATION OR *
- * DISTRIBUTION FEES. *
- * *
- **********************************************************************
-
-
- ITALY ( AND REST OF THE WORLD )
- =====
-
- In order to register yourself you have to fill out the registration
- form in "MM:Registration/World" and send it, together with the
- registration fee to:
-
- Giuseppe Aliberti
- via delle Fontanelle
- 67016 Paganica (AQ)
- ITALY
-
- You can optionally fill out the registration form with a text editor
- and send it via netmail ( CRASH MAIL ONLY ) to 2:335/602.2.
-
- It is also possible to register MUI together with Mail Manager, there
- is a special bundle offer, and you will get the MUI keyfile together
- with the Mail Manager one.
-
- The registration fee for Mail Manager is:
-
- Point Only Full Node
- ----------------- ------------------
- Itl Lire 50000 (35000) 100000 (85000)
- DM 50 (35) 100 (85)
- US $ 35 (25) 70 (60)
- UK £ 23 (15) 46 (38)
-
-
- The registration fee for Mail Manager together with MUI is:
-
- Point Only Full Node
- ----------------- ------------------
- Itl Lire 75000 (60000) 125000 (110000)
- DM 73 (58) 123 (108)
- US $ 50 (40) 85 (75)
- UK £ 33 (25) 56 (48)
-
-
- The fee between brackets is reserved only to Registered Users of Point
- Manager v3.10 and higher.
-
- You can send money as cash, but please, be careful.
- The safest and easiest way to send your registration fee is to use an
- International Postal Money Order, in this case USE ONLY International
- Postal Money Orders in ITALIAN LIRE (Italian Users can send me a
- Vaglia Postale). Your local post office will happily provide you with
- more information about this.
- You can also use an Eurocheque in Italian Lire.
-
- I WILL NOT accept any other type of payment !
-
-
- GERMANY
- =======
-
- Please refer to the German version of the Manual. Thanks !
-
-
-
- 4.3 About MUI
-
- MUI is a system to generate and maintain graphical user interfaces.
- With the aid of a preferences program, the user of an application has
- the ability to customize the outfit according to his personal taste.
-
- MUI is distributed as shareware. To obtain a complete package
- containing lots of examples and more information about registration
- please look for a file called "muiXXusr.lha" (XX means the latest
- version number) on your local bulletin boards or on public domain
- disks.
-
- MUI is (c) Copyright 1992-94 by Stefan Stuntz
-
-
-
- 4.4 MUI Hints & Tips
-
- Here there are only a few hints to improve your Mail Manager GUI:
-
- The numbers specified with the \<n> sequence in the Area Name are not
- the numbers of the corresponding color in the screen palette but the
- numbers of the System Pen you want to use, in particular:
-
- 0 - Detail
- 1 - Block
- 2 - Text
- 3 - Shine
- 4 - Shadow
- 5 - Fill
- 6 - Filltext
- 7 - Background
- 8 - Highlight
-
- You can assign to every pen the color you prefer from the Edit Palette
- window of the MUI Prefs. [System -> Select the right screen from the
- popup -> Edit -> Palette].
-
- For example these are my Screen Colors and my System Pens assignments:
-
- Screen Colors
- ---------------
-
- Color Red Green Blu
-
- 0 149 149 149 Grey
- 1 0 0 0 Black
- 2 255 255 255 White
- 3 59 103 162 Sky-Blue
- 4 123 123 123 Dark-Grey
- 5 175 175 175 Light-Grey
- 6 255 255 0 Yellow
- 7 255 169 151 Pink
-
-
- System Pens
- ---------------
-
- Pen Color Assigned
-
- 0 - Detail 0 Grey
- 1 - Block 1 Black
- 2 - Text 1 Black
- 3 - Shine 2 White
- 4 - Shadow 1 Black
- 5 - Fill 3 Sky-Blue
- 6 - Filltext 2 White
- 7 - Background 0 Grey
- 8 - Highlight 6 Yellow
-
-
- So with \3 the text will be White and with \8 the text will be Yellow.
-
- Another hint: normally MUI uses, as default colors for the different
- selection state of a ListView entry, three colors really much alike.
- This is an unlucky choice ! There is a big difference between an
- active entry ( the one with the cursor on ), and a selected entry.
-
- I've solved the problem by using the following colors (from the Images
- window of MUI Prefs):
-
- BG Listview Cursor Pen -> Colormap -> Color n-1 (color 7)
- BG Listview Selected Pen -> Colormap -> Color 3
- BG Listview Selected+Cursor Rast-> Fill/Back Raster
-
-
-
- 4.5 Licence Agreement
-
- Mail Manager is offered to you under the concepts of ShareWare.
- You can use it for an evaluation period of up to 4 weeks without
- paying any charge. If you are going to use Mail Manager after the
- evaluation period, you MUST register.
- By copying, distributing and/or using the program you indicate your
- acceptance of this license to do so, and all its terms and conditions.
-
- You May:
- - install and use this software for your personal use on a single
- microcomputer
- - make verbatim copies of the original distribution archive without
- any files being omitted/added/changed.
- - distribute those copies of the software if NO charge is asked for,
- except for the media.
- - upload the software to as many BBSes as you like
-
- You May NOT:
- - copy and/or distribute this program without the accompanying
- documentation and other additional files that come with the
- original distribution archive.
- - alter the software and/or the accompanying files in any way
- - copy and/or distribute modified version of this program.
- - decompile, disassemble, translate, convert to another programming
- language or otherwise reverse engineer the software.
- - grant sublicences, leases or other rights in the software
- - rent the software to others
-
- The program is released "as is", without any warranty, either
- expressed or implied, and in no event I will be liable for any
- damages caused by the use of this program.
-
-
-
- 4.6 Acknowledgements
-
- The following names are either trademarks or the efforts of the person
- and/or company listed:
-
- Amiga and AmigaDOS are trademarks of Commodore-Amiga, Inc.
- Fido and FidoNet are trademarks of Tom Jennings, Fido Software.
- ARexx by William S. Hawes, Wishful Thinking Development Corp.
- MUI by Stefan Stuntz
- MagicWb by Martin Huttenloher
- EMS by Davide Masserenti
- Spot by Nico Francois
- TrapDoor by Maximilian Hantsch and Martin Laubach
-
-
- Many thanks to:
-
- Alessandra (Ciccia) For her love !
-
-
- ...and to the BEST BetaTesting team:
-
- Edwin Halsema the beta tester that every programmer wants.
- ........ or never wants ?! *:^]
-
- Eric Krieger for his fantastic help during the testing
- phase and for his fantastic translation of
- the docs in AmigaGuide format.
-
- Siggi Weisner -- German Registration and Support site --
- For his fantastic help during the testing
- phase, for his German translation, for his
- help with the German users and for being
- a fantastic friend. Many Thanks also to
- Claudia, for her patience !
-
- Maurizio Fabiani The Boss !!! For his support, for
- permitting me to know Fidonet and for MAUI
- for AMIGA, the best BBS for Amiga Users.
-
- Massimo Brogioni The first Node that installed Mail Manager.
- Thanks Massimo for your trust and for all
- your incredible help !
-
- Paolo Carotenuto I've simply no words ! You are great Paolo,
- maybe the greatest !
-
- Robert Hofmann Do you want your program to be a great one ?
- Ask Robert to be a BetaTester, but please be
- careful, high doses could be lethal ! *:^]
-
- Marco Musso For the installation script, for the Italian
- translation and for his help during the
- testing phase, he always has a good
- suggestion.
-
- Stig Poulsen He wasn't one of the firsts to join the Mail
- Manager Project, but he is a great tester
- and he should have joined the project
- before !
-
- Frank Geider For his suggestions and for the French
- translation.
-
- Gaetano Ble' for his help, and for his hospitality.
-
- Ferran Delriu For his support.
-
- Andreas Mann For his suggestions and Bug reports.
-
- Andreas Netscher For his suggestions and Bug reports.
-
-
- many many thanks also to:
-
- Angelo Verdone, Bernd Ernesti, Cristiano Zanella, Felice Murolo,
- Riccardo Vratogna, Andrea Modenese, Danilo Aghemo, Piergiorgio
- Ghezzo, Gianmarco Giovannelli, Erik Boersting, Stefan Bauer,
- Frederic Aleixendri, Eugene Stepanoff, Regis Rampnoux, Matteo Penna,
- Florent Monteilhet, Federico Medolago Albani, Sandro Tolaini.
-
-
-
-
-
-
-
-
- "Omne tulit punctum, qui miscuit utile dulci"
-
- (Orazio, Arte Poet., 343)
-
-
-